@Emulatorman

How do you decide which versions of packages to have? Since hyperbola is LTS, I guess the latest versions would not be appropriate for it.

Say, there's python-cryptography versions from last 2.3 which hyperbola had in v0.3 to latest 3.2.1 . How do you decide which python-cryptography to have?

Milky Way v0.4 is based on the Debian's BullsEye generation. We made a modification in the development releases, you can see here for further details.

How do you decide which versions of packages to have? Since hyperbola is LTS, I guess the latest versions would not be appropriate for it.

Say, there's python-cryptography versions from last 2.3 which hyperbola had in v0.3 to latest 3.2.1 . How do you decide which python-cryptography to have?

We won't support GNOME or wayland in the next version (v0.4) because we are removing all GNU/Linux-based desktop frameworks (ConsoleKit, PolicyKit, D-Bus, systemd, elogind, etc..). Our focus is become a lightweight distro and a BSD descendant operating system (HyperbolaBSD), so our packages in that version will be migrated to BSD-based ones to ease the migration from GNU/Linux to HyperbolaBSD.

This is the best distro ever

dikasp2 wrote:

how about lxde or xfce desktop, is there any possibilities to port them into hyperbola 0.4 ?

As far as I know, XFCE forces Polkit and needs at least ConsoleKit to make work while i'm not sure about LXDE.

Had done short search for getting away from those dependencies. Found the following here in the Gentoo-Wiki (https://wiki.gentoo.org/wiki/LXDE):

It's a pity, but LXDE seems therefore not fitting into the way as desktop-environment. And well: https://l3net.wordpress.com/2013/03/17/ … -desktops/

Yes, those comparisons are most helpful in the time they were done (the one I've found here was done back in 2013). But the generic comparison won't have changed that much. Especially when looking on the small environments.

how about lxde or xfce desktop, is there any possibilities to port them into hyperbola 0.4 ?

As far as I know, XFCE forces Polkit and needs at least ConsoleKit to make work while i'm not sure about LXDE.

So, ALL debian patches are applied to the source code of those packages and later, it is built by the arch PKGBUILD method. Correct me if I'm wrong.

Yes, it is in fact.

Ok, i will let you know when v0.4 is ready to begin make testing.

Currently we are near (95%) to complete [core], then we need rebuild all xenocara + mesa packages (same version from v0.3). So, under this stage, we should build at least GTK and Qt to begin push the first packages (DEs, WMs, DMs, applications, etc). Anyway, i think a list of packages requested by community should be the way, however those packages should be as lightweight as possible. If there is an option for that which  doesn't force GNU/Linux-based frameworks (D-Bus, logind/ConsoleKit, Polkit, etc) then it can be considered.

how about lxde or xfce desktop, is there any possibilities to port them into hyperbola 0.4 ?

I'm using xfce and would love to see it return, but I'm not optimistic given that the devs haven't had the resources to keep it up-to-date in 0.3.

My guess is that if keeping xfce up-to-date for hyperbola was a frictionless task they would already be doing it, and that the refined focus on "lightweight" packages is being done to minimize the amount of maintenance so they can prioritize the work on hyperbolaBSD at the moment.

All Debian patches come from debian/patches folder.

I suppose it should be ready in 2~3 months, it will depend of stability of our new packages and help of community to test our new version when it is available for that.

So, ALL debian patches are applied to the source code of those packages and later, it is built by the arch PKGBUILD method. Correct me if I'm wrong.

Great. I'm in for testing. I'll keep checking for v0.4 on Downloads page. Hopefully, it would have enough packages such that I move from parabola to hyperbola permanently.

If you have some page where you list upcoming packages (which you will be building in the upcoming week) (with versions) to be built, we (community) can build it (write PKGBUILD). I presume currently, there are some dependencies to be built first.

Also, you don't have to trust the community, you can reject PKGBUILD made by community if you find it strange and unacceptable for Hyperbola's standards. It will reduce your work and help forming a community.

eg. You have patches here in this gnupg-stable prepare function. Where did they come from?

https://git.hyperbola.info:50100/packag … e/PKGBUILD

All Debian patches come from debian/patches folder. You can search gnupg2 in their package search page -> https://packages.debian.org/search?suit … rds=gnupg2

Then, download gnupg2_2.2.20-1.debian.tar.xz from https://packages.debian.org/source/bullseye/gnupg2

I suppose it should be ready in 2~3 months, it will depend of stability of our new packages and help of community to test our new version when it is available for that.

We won't support GNOME or wayland in the next version (v0.4) because we are removing all GNU/Linux-based desktop frameworks (ConsoleKit, PolicyKit, D-Bus, systemd, elogind, etc..). Our focus is become a lightweight distro and a BSD descendant operating system (HyperbolaBSD), so our packages in that version will be migrated to BSD-based ones to ease the migration from GNU/Linux to HyperbolaBSD.

Sounds fantastic. Please have more packages in hyperbola v0.4. It's the biggest problem with Hyperbola today.

I tried to build python-cryptography earlier but I wasn't able to. My concern was which patches to use. Were the patches made by you yourself or you took it from somewhere?

eg. You have patches here in this gnupg-stable prepare function. Where did they come from?

https://git.hyperbola.info:50100/packag … e/PKGBUILD

When will v0.4 be completed for release approximately?

you may ask the main developer to confirm this if you curious

in meantime you can check for yourself the list of all available packages:
[stable]
https://repo.hyperbola.info:50012/gnu-p … le/sources/
[testing]
https://repo.hyperbola.info:50011/gnu-p … g/sources/