Portage: mgorny creates a fork

[blopsalot]

[Naib]

THAT is the exact definition of malice...
They screwed up and THAT is not the behaviour that should be championed. If there are issues create a fork and convince everyone your fork is better. You do not take over


I do not care whether they are playing nice at the moment, at some point it was thought that was a good idea AND it never is. Such methodologies should not be championed as why forks are good.... Some time ago a hostile attempt was made on Gentoo by a cabal of developers, imagine if they did this with the infrastructure! Messing with the users for their own gains
_________________
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;

[blopsalot]

[krinn]

Some Lords didn't like the King, so the Lords have the brilliant idea to put cholera over the country, ah, yes, well, who cares about people as long as it bug the King.
It the mean time, someone discover cure for cholera

later...

[blopsalot]

[krinn]

[Naib]

[blopsalot]

and the world turns.
https://ffmpeg.org/pipermail/ffmpeg-devel/2015-July/176489.html

[Naib]

Gosh I guess giving the populous cholera was worth it just to usurp the king
_________________
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;

[blopsalot]

I was pulling these packages from git, so I dunno what happened in the tree. make uninstall make install... Was libav forced in gentoo at one time?

[Naib]

[Yamakuzure]

Well, in the dev ml mgorny said, that his fork will not diverge too much from mainline portage, so badass crazy ideas will have no chance anyway.

[blopsalot]

Getting back on topic. What kind of schedule do you think Gentoo should follow in regards to EAPI deprecation? That seems to be the matter in contention here.

[NeddySeagoon]

blopsalot,

That depends on your point of view.
It makes no difference to package managers since they need to support EAPIs no longer it the tree to be able to remove old packages.
For package maintenance, the current EAPI and the one before, as a rule of thumb. Depending on the frequency of new EAPIs, maybe more.

I would hate to see the toolchain broken by a too hasty EAPI bump.

Then again, if its not broken why fix it?
Updating an ebuild only for an EAPI change is not really useful work and it needs to be a revision bump, so everyone will be doing useless rebuilds, as the installed code should not change.
_________________
Regards,

NeddySeagoon

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

[blopsalot]

[mv]

[Ant P.]

[skellr]

[Naib]

[beandog]

Just some anecdotal stuff here from me.

I'll "fork" something in the sense of make my own repo (that may or may not be public) and then hack on it and maybe *eventually* send it back upstream.

Here's some thingies though:

* forking stuff is one way of making your own project, without having to move at the speed and development style of upstream. People can see your changes, and they can cherry pick them and format them the way they like it or not
* it can be a bit antagonistic or scary to poke upstream, and so it's not worth the effort to reach out
* you consider your changes so minor that its not relevant towards kicking back to someone
* don't want to go through the effort to open a bug
* language barriers
* you don't know how to code in the language but you've figured out a way to hack it so it does what you like

So, there's not just technical reasons to fork something, but social as well.

I do do like mgorny does, and work on both projects. dvd_info is a fork of lsdvd in functionality, but mine goes way past it. I do work on lsdvd when I feel like there's something reasonable to add back into that program too, though, because it's a clean feature that could be added, *and* it already has traction across multiple distros.
_________________
If it ain't broke, tweak it. dvds | blurays | blog | wiki

[Juippisi]

[Yamakuzure]

[Zucca]

I sometimes feel that "--force" in several different package mangers should be replaced with something like the one in efl.
Because I've seen people hitting "y" even if --force was used and the program warns about it and wants a confirmation.
By forcing people (see what I did there?) to write some long string that itself warns about the possible consiquences might have more effect.
_________________
..: Zucca :..

[Dr.Willy]

[krinn]