Re: [blfs-dev] QA in BLFS

2018-03-04 Thread Tim Tassonis
On 03/04/2018 07:26 PM, Bruce Dubbs wrote: Thomas Trepl wrote: Another example is creating users for some packages. It is not required to have the user postfix on the building system, the user should be there on the system where postfix gets installed. So, the user postfix is a requirement

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] QA in BLFS

2018-03-04 Thread Bruce Dubbs
Thomas Trepl wrote: Another example is creating users for some packages. It is not required to have the user postfix on the building system, the user should be there on the system where postfix gets installed. So, the user postfix is a requirement in the install phase which might occur on very

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

Re: [blfs-dev] QA in BLFS

2018-03-04 Thread Richard Melville
On 4 March 2018 at 02:11, Bruce Dubbs wrote: > > I have run into that with the package currency scripts. About 65% of the > packages can be automated quite easily, but the other third require a > custom procedure for each package. Look at just package names for >

Re: [blfs-dev] QA in BLFS

2018-03-04 Thread Thomas Trepl
Am Samstag, den 03.03.2018, 13:02 +0100 schrieb Pierre Labastie: > Hi, > > Now that 8.2 is out, I'd like to share some thoughts about testing > the book > instructions (OK, QA in the subject may be slightly too ambitious). > > We (mainly Bruce) have updated an average of 4 packages per day >

Re: [blfs-dev] mutt without ssl

2018-03-04 Thread Ken Moffat
On Fri, Mar 02, 2018 at 09:49:30PM +, Ed Batalha wrote: > > Hi, > > Given that openssl is now in LFS, shouldn't mutt be built --with-ssl > by default? > The command in BLFS still doesn't include this, but the option is > discussed further down the page. > In my humble opinion ssl shouldn't