Re: [blfs-dev] A few suggestions including a package manager

2018-03-04 Thread Bruce Dubbs
Hendrik Hoeth wrote: Hi, Thus spake Pierre Labastie (pierre.labas...@neuf.fr): On 04/03/2018 06:34, m...@pc-networking-services.com wrote: 1) You could make another svn clone of the current rolling release repository [...] Well, not sure it would bring much: svn merging is usually hard,

Re: [blfs-dev] A few suggestions including a package manager

2018-03-04 Thread Richard Melville
On 4 March 2018 at 15:41, Pierre Labastie wrote: > On 04/03/2018 06:34, m...@pc-networking-services.com wrote: > > > 2) There is a package manager already that works on building from source > > code. It is called nix https://nixos.org/nix/. I have off and on > looked >

Re: [blfs-dev] A few suggestions including a package manager

2018-03-04 Thread Hendrik Hoeth
Hi, Thus spake Pierre Labastie (pierre.labas...@neuf.fr): > On 04/03/2018 06:34, m...@pc-networking-services.com wrote: > > > > 1) You could make another svn clone of the current rolling release > > repository [...] > > Well, not sure it would bring much: svn merging is usually hard, Which is

Re: [blfs-dev] A few suggestions including a package manager

2018-03-04 Thread Pierre Labastie
On 04/03/2018 06:34, m...@pc-networking-services.com wrote: > Hello, > > From reading the QA thread I have a couple of suggestions: > > 1) You could make another svn clone of the current rolling release > repository and have that as a private repository for updates. This > *could* give editors

[blfs-dev] A few suggestions including a package manager

2018-03-03 Thread me
Hello, From reading the QA thread I have a couple of suggestions: 1) You could make another svn clone of the current rolling release repository and have that as a private repository for updates. This *could* give editors breathing space as the frantic updates could still be done, but have this