A fork that claims that it will never be a "mainstream" thing because others invested more resources for a more advanced Portage improvement without their work being rewarded makes me wonder if this is not just another "me too" project. The NIH is strong in Open Source land._________________I already use the new Genthree.

There are many threads about improving Portage therefore you may be interested by this new: mgorny creates a fork.

Split from the 2014 thread as this is a new effort and not directly related to the events from 4 years ago._________________The First of April. The day when people critically evaluate information from the internet before accepting it as true.

I don't mind portage moving slowly ... the first requirement for a Package Manager is that it 'does the right thing', that changes with time.
For some things, I'm happy with 'last out of the past' rather than 'first into the future' :)

I get enough excitement from ~arm64 without wondering if the package manager has done the right thing._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Don't misunderstand me: I still get my thrill off systems which still work with 30-year-old manuals. But a little more speed while calculating dependencies is something I would like to see._________________I already use the new Genthree.

Well, mgorny has done a lot to portage. Sent many patches on different things and has worked on EAPI 7 probably more than anyone. I can understand how he feels when the patches are not getting to main portage, but fragmenting an already smallish distro doesnt sound good either.

Of course, Gentoo is more than just software. It is also a community around the distribution. Gentoo benefits from around 250 developers and thousands of users, many of which are experts in their fields. The distribution project provides the means for the users to enjoy Gentoo: documentation, infrastructure, release engineering, software porting, quality assurance, security followup, hardening, and more.

What's the long-term plan? It's unlikely for this fork to replace
Portage. However, its goal is to follow the example set by projects
such as libav and libressl. They never became mainstream but they made
the respective original projects 'wake up' and start solving at least
some of the problems that were ignored before. Hopefully this project
will also make Portage developers reconsider their attitude and start
working on improving Portage rather than just keeping it alive.

This is why I love open source.
That fork can be seen as a test platform for proof of concepts. I more than welcome project like this. It's good for the Portage project and community._________________..: Zucca :..

This is why I love open source.
That fork can be seen as a test platform for proof of concepts. I more than welcome project like this. It's good for the Portage project and community.

Yea, but the fact that he used libav as an example is a little stunning. The reason I refused to to within 1,000 miles of that one was their decision to use the same fucking library names as ffmpeg...just to force everyone to make a choice. That's not "waking up" anyone. That's just being the biggest dick in the room.

krinn, on the other hand Portage should not be in the business of supporting out-of-tree packages just because some users refuse a dependency based on vague feelings. You should not base your critique of the fork on that particular bug though, it has nothing to do with it._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

krinn, I don't know the background of that particular fork and its history. My post should maybe looked at more general level of why forks of open source projects usually tend to cause only good progress.

I saw that the README not written in the most polite way towards the current "mainline" Portage developerrs. Sadly. I still hope this wouldn't affect the cooperation efforts of these two pprojects. But yeah, it surely doesn't help the cooperation either. _________________..: Zucca :..

This is why I love open source.
That fork can be seen as a test platform for proof of concepts. I more than welcome project like this. It's good for the Portage project and community.

Yea, but the fact that he used libav as an example is a little stunning. The reason I refused to to within 1,000 miles of that one was their decision to use the same fucking library names as ffmpeg...just to force everyone to make a choice. That's not "waking up" anyone. That's just being the biggest dick in the room.

Tom

The reason I steered well clear of libav was seeing it in vulnerability alerts weekly, each with a long list of CVE-${two_years_old} numbers dated from when ffmpeg fixed them, meanwhile they were busy sneering about how they were the new upstream. Good riddance to that trash and everyone to blame for it.