You must be kidding , more than 1000

Please explain

Code:
Installed packages to be REMOVED:
    py312-datasets: 5.0.0

Number of packages to be removed: 1
Number of packages to be installed: 44
Number of packages to be upgraded: 1023
Number of packages to be reinstalled: 17

The process will require 5 GiB more space.
10 GiB to be downloaded.
 
sorry i complain what a hell,
-> 3.11 => 3.12
root@myfreebsd:/etc # cat make.conf | grep -i python
DEFAULT_VERSIONS+=python=3.12
 
Just be thankful you aren't required to deal with it multiple times a year and the fact that if it somehow fails your entire ability to manages packages/ports goes poof. One of the main reasons I was forced to abandon my use of Gentoo despite how good the ecosystem (and community) around it is.
 
I use redcore (gentoo clone). Feel free to advice.
My reasons for leaving Gentoo are more than just its package manager (portage) being written in python. I was just trying to point out that any time python targets change for portage things can go south very quickly. There have been more than a few attempts to either re-write or clone portage in C and various other programming languages. But most of them are abandoned, never got wide use and/or aren't 100% compatible with Gentoo's repos (ebuilds/EAPI). So, you're better off just dealing with portage and all the issues that come along with using it. Mainly, the python issue and the fact that it runs very slow.

There is even an entire distro inspired by Gentoo and portage called SourceMage. Which while very nice is probably only used by like 10 people in the entire world. Instead of python its package manager was built 100% with bash scripting. Which avoids the main issue with portage while still giving you something similar to USE flags. But since no one uses it you're on your own instead of having access to Gentoo's official repo ebuilds and all of the custom overlays filled with ebuilds many people have shared over the years.

Gentoo itself has added support for binaries in portage and started providing binary packages for all ebuilds as of a couple of years ago so I don't see any reason to use any of the many "Gentoo with pre-compiled packages" downstream distros anymore. Funtoo was the only fork of the Gentoo project where anything exciting was happening but development of it stopped a year ago. So now if you're going to play around in the Gentoo ecosystem you're best off sticking with Gentoo itself. It has heavily been moving towards providing a much easier installation process and even ships a pre-compiled kernel these days with all modules enabled by default. IIRC their distribution kernel as they call it is the same configuration as the one shipped by Debian.

The killer feature of portage are the USE flags and ebuilds being relatively easy to write. But Gentoo is converging with the rest of the mainstream binary distros now (Fedora, Debian, Arch and all the other ones shipping systemd by default). So a lot of the power you used to get with portage is starting to go away due to this and recent changes to the EAPI that ebuilds are expected to follow. In other words maintaining your own custom "distro" through portage that is different from the modern Linux/Red Hat/Debian/systemd as PID1 default is getting harder with each passing years now. Gentoo/portage is still a "meta-distribution" where you can highly customize the entire system and all packages on it through USE flags but maintaining said system is now much harder than it was in the past. Hence why I've moved away from it. If I'm going to have to do a bunch of work then there was no longer any point in having to live with portage itself.

As far as python goes it's just a mess. I use it for some other things. But the main difference for me is now I don't have to worry about python breaking lower userspace in my system. Since my package manager is no longer reliant on it. Unlike the BSDs portage can easily break my "base system" leaving me in a state where it can be very hard to recover when something goes wrong (well more annoying to recover). With portage you have to manually manage python targets through make.conf and package.use/.mask. Very often there are ebuilds that want older/newer versions of python. Semi-often an announcement comes out that portage itself is being moved to a newer version. Whenever python targets change it usually means you're going to be rebuilding a lot of stuff installed on your system. Dealing with python targets changing often gets old really fast.

Then there is the whole python 2.x vs. 3.x thing. Python was much easier to deal with before python 3.x came out. Lots of stuff I still use never got re-written for 3.x. So when using Gentoo it means a lot of stuff listed in my package.use file to manually force certain packages/ports to use the correct version of python it needs (a lot of 3.x stuff wants particular versions as well).

One of the main things I use that requires Python is vapoursynth (a video frameserver). I've found the easiest way to deal with it is having it live in a chroot where I can keep all those python scripts away from the rest of my system. Since all I need to do is pipe video into and out of that chroot it works fine. This way I can also have multiple versions of vapoursynth installed as well since that is a whole can of worms on its own (mostly due to it relying so heavily on python scripting and video/audio codecs).

Python is just annoying like this in general. I don't want anything in my base system requiring it. I avoid stuff like pip like it's the plauge.
 
My project rejected python years ago for similar reasons. We have some perl 5, that's bad enough, but at least it's moderately stable. We try and use shell a lot of the time. To be fair, Perl can be extremely useful at times, too.
 
It should be 1 programming suite where all different details are options but they can't get unified internally. Result is a dependency tree in their own room.
 
My reasons for leaving Gentoo are more than just its package manager (portage) being written in python. I was just trying to point out that any time python targets change for portage things can go south very quickly. There have been more than a few attempts to either re-write or clone portage in C and various other programming languages. But most of them are abandoned, never got wide use and/or aren't 100% compatible with Gentoo's repos (ebuilds/EAPI). So, you're better off just dealing with portage and all the issues that come along with using it. Mainly, the python issue and the fact that it runs very slow.

There is even an entire distro inspired by Gentoo and portage called SourceMage. Which while very nice is probably only used by like 10 people in the entire world. Instead of python its package manager was built 100% with bash scripting. Which avoids the main issue with portage while still giving you something similar to USE flags. But since no one uses it you're on your own instead of having access to Gentoo's official repo ebuilds and all of the custom overlays filled with ebuilds many people have shared over the years.

Gentoo itself has added support for binaries in portage and started providing binary packages for all ebuilds as of a couple of years ago so I don't see any reason to use any of the many "Gentoo with pre-compiled packages" downstream distros anymore. Funtoo was the only fork of the Gentoo project where anything exciting was happening but development of it stopped a year ago. So now if you're going to play around in the Gentoo ecosystem you're best off sticking with Gentoo itself. It has heavily been moving towards providing a much easier installation process and even ships a pre-compiled kernel these days with all modules enabled by default. IIRC their distribution kernel as they call it is the same configuration as the one shipped by Debian.

The killer feature of portage are the USE flags and ebuilds being relatively easy to write. But Gentoo is converging with the rest of the mainstream binary distros now (Fedora, Debian, Arch and all the other ones shipping systemd by default). So a lot of the power you used to get with portage is starting to go away due to this and recent changes to the EAPI that ebuilds are expected to follow. In other words maintaining your own custom "distro" through portage that is different from the modern Linux/Red Hat/Debian/systemd as PID1 default is getting harder with each passing years now. Gentoo/portage is still a "meta-distribution" where you can highly customize the entire system and all packages on it through USE flags but maintaining said system is now much harder than it was in the past. Hence why I've moved away from it. If I'm going to have to do a bunch of work then there was no longer any point in having to live with portage itself.

As far as python goes it's just a mess. I use it for some other things. But the main difference for me is now I don't have to worry about python breaking lower userspace in my system. Since my package manager is no longer reliant on it. Unlike the BSDs portage can easily break my "base system" leaving me in a state where it can be very hard to recover when something goes wrong (well more annoying to recover). With portage you have to manually manage python targets through make.conf and package.use/.mask. Very often there are ebuilds that want older/newer versions of python. Semi-often an announcement comes out that portage itself is being moved to a newer version. Whenever python targets change it usually means you're going to be rebuilding a lot of stuff installed on your system. Dealing with python targets changing often gets old really fast.

Then there is the whole python 2.x vs. 3.x thing. Python was much easier to deal with before python 3.x came out. Lots of stuff I still use never got re-written for 3.x. So when using Gentoo it means a lot of stuff listed in my package.use file to manually force certain packages/ports to use the correct version of python it needs (a lot of 3.x stuff wants particular versions as well).

One of the main things I use that requires Python is vapoursynth (a video frameserver). I've found the easiest way to deal with it is having it live in a chroot where I can keep all those python scripts away from the rest of my system. Since all I need to do is pipe video into and out of that chroot it works fine. This way I can also have multiple versions of vapoursynth installed as well since that is a whole can of worms on its own (mostly due to it relying so heavily on python scripting and video/audio codecs).

Python is just annoying like this in general. I don't want anything in my base system requiring it. I avoid stuff like pip like it's the plauge.
Give redcore a try. Once configured , i hardly play with flags.
 
And to make matters worse, you have to use BOTH pkg and pip to maintain various Python packages. This is a big mess and a pain. I don't know of a good solution.
Summarize the things you need it for and build it per case in a jail. I need it for Qemu 11. No idea why. Something can't be C? 11 is a little faster so still worth the effort.
 
Summarize the things you need it for and build it per case in a jail. I need it for Qemu 11. No idea why. Something can't be C? 11 is a little faster so still worth the effort.
That makes the amount of work to be done even larger. But at least it gets rid of side effects, and makes the work more systematic.
 
Back
Top