[sage-devel] Packaging rant

2015-06-11 Thread Jeroen Demeyer
On 2015-06-11 03:40, François Bissey wrote: * fork upstream and keep it as a separate package but no one really wants to be the maintainer. If it's decided that we are allowed to fork polybori, can this be applied to other packages too? I have often been frustrated in Sage by people complain

Re: [sage-devel] Packaging rant

2015-06-11 Thread Julien Puydt
Hi, Le 11/06/2015 10:28, Jeroen Demeyer a écrit : On 2015-06-11 03:40, François Bissey wrote: * fork upstream and keep it as a separate package but no one really wants to be the maintainer. If it's decided that we are allowed to fork polybori, can this be applied to other packages too? I hav

Re: [sage-devel] Packaging rant

2015-06-11 Thread Francois Bissey
I am only proposing to fork a package with a dead upstream. I wouldn’t do it with a live one. Nevertheless I understand that it makes me look like I am saying two contradictory things at the same time. To be clear with a rant of my own. If you fork a live project you’ll have to live with the div

Re: [sage-devel] Packaging rant

2015-06-11 Thread mmarco
Upstream being dead, the only alternative to forking is to live forever with a fixed version. That might work for the moment, but eventually we will find issues with newer compilers, or newer version of the libraries it deppends on, or the newer version of python And at that point forking

Re: [sage-devel] Packaging rant

2015-06-12 Thread Jeroen Demeyer
On 2015-06-11 10:31, Julien Puydt wrote: Open software is about cooperation. Of course. The question is: what should we do if upstream does not want to cooperate? I don't want to call names in this thread, but I have proposed patches to many upstream projects which are part of Sage (usually th

Re: [sage-devel] Packaging rant

2015-06-12 Thread Francois Bissey
> On 12/06/2015, at 21:18, Jeroen Demeyer wrote: > > On 2015-06-11 10:31, Julien Puydt wrote: >> Open software is about cooperation. > Of course. The question is: what should we do if upstream does not want to > cooperate? I don't want to call names in this thread, but I have proposed > patche

Re: [sage-devel] Packaging rant

2015-06-12 Thread Julien Puydt
Hi, Le 12/06/2015 11:18, Jeroen Demeyer a écrit : On 2015-06-11 10:31, Julien Puydt wrote: Open software is about cooperation. Of course. The question is: what should we do if upstream does not want to cooperate? I don't want to call names in this thread, but I have proposed patches to many up

Re: [sage-devel] Packaging rant

2015-06-12 Thread Jeroen Demeyer
On 2015-06-12 14:32, Julien Puydt wrote: Nothing will slow development down like dozens of forked packages to maintain, especially if upstreams consider you hostile. If you mean "forking" in the serious sense, you're probably right. If you mean "forking" as in "add a few patches", then you're

Re: [sage-devel] Packaging rant

2015-06-12 Thread Paulo César Pereira de Andrade
2015-06-12 6:18 GMT-03:00 Jeroen Demeyer : > On 2015-06-11 10:31, Julien Puydt wrote: >> >> Open software is about cooperation. > > Of course. The question is: what should we do if upstream does not want to > cooperate? I don't want to call names in this thread, but I have proposed > patches to man