On 4 March 2018 at 15:41, Pierre Labastie <pierre.labas...@neuf.fr> 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 > > at this, and it was only through reading the documentation on it, that I > > found that it can be made to use source only builds by moving the default > > location, so that it will not download ANY binary builds. > > > > For me it gave me a really bad headache as you need to learn the nix > > language and add the build scripts, much like jhalfs does. What this > > package manager does is install in a DEST-DIR. Each package has its own > > directory. It may well be that some of the programmers, on the team may > > find it very easy to add the scripts. If this could be made to work at > > the LFS stage then any packages added on at the BLFS stage would get > > automatically added to the nix package repository. > > > > It may also take a little of the stress out of security updates as you > are > > also able to check for updates. If this could be achieved then future > > upgrade/downgrade of packages could be rather painless. > > > > The adaption to this sort of package manager would be a task too big for > a > > single person to do. It might be worth thinking about, as a long-term > > goal. Even if a programmer had an hour or so spare without real life, > > updating the book every so often they could add the build scripts. > > > > Thanks for the suggestion. I'll have a look at nix to include it in jhalfs. > Maybe GNU Guix is a better bet; it's built on Nix, but instead of having to learn a language that can't be used anywhere else, Guix uses Guile, which is much more useful. > > I do not think rebuilding all the dependencies of a package each time it is > updated is necessary: some packages like qt5 have more than 250 > dependencies > at the recommended level (and more than 400 at the optional level). It > would > not be reasonable to rebuild all of those. OTOH, it'd be nice to be able to > build a package in an environment where only the listed dependencies are > installed (well, sometimes added packages may break things, like for > File::BaseDir, where the tests do not pass if xdg-user-dirs is installed > and > XDG_CONFIG_HOME is set). I understand nix is able to do that (insulate > building from the system). Actually, I'm almost sure the apt/dpkg suite > can do > that too (there is a "chroot" mode for apt-build). Right now, I use porg: > it > is very basic, but at least, there is almost no language to learn. > Building in > insulation would involve setting the chroot manually... But I am not up to > that yet. > +1 for porg. Richard
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
