Jeremy Huntwork wrote:
Matthew Burgess wrote:
If anyone wants any other features included now's the time to get
those requests in. At the moment, I'm considering branching off for
stabilisation in around 4 weeks time (though with that being very
close to Christmas, it may slip a little). Only time will tell if
that schedule's too ambitious, but at least it gives us something to
aim for.
This is kind of a brave request, and I'm fully prepared to be shot down.
In fact, I think I'd be surprised if the group went for it. ;) However
after thinking about this for some time, I'm going to venture a request
and see what comes of it.
I've been reading and attempting to apply in my spare time Matthias
Benkmann's hint, 'More Control and Package Management using Package
Users'. There are *many* aspects of that hint that I find extremely
helpful and useful, especially from an educational perspective.
Especially I like knowing what things are being installed setuid root
and why and knowing what packages are 'broken' in that they try
unecessarily change ownership or permissions on files.
LFS is good as it is, however there are still many aspects of the system
that the user is not shown or given explanations about. Matthias'
approach broadens the field a bit.
So. I had been thinking it would be nice if LFS and BLFS adopted (some
of) this approach. Again, I fully recognize that this is new ground in a
way and that many people will think, "it is a hint and should stay a
hint", but, IMHO, there are many techniques employed here that a default
LFS user could learn from and benefit by.
--
JH
I guess that would depend on how much is "some of". I've seen a lot of
people reporting strange problems when using this hint (or maybe that's
because a lot of people that try it don't really know what they're
doing, kinda like many people who are trying to build LFS now...). I do
like it in principle, but I've never used it because I generally just
prefer to take the "rebuild whole system to upgrade anything" approach,
so using pretty much any kind of package management is overkill. Yes, I
realize that it is more than package management, and it certainly is
good to know what is installed on your system. Again, this goes back to
"which parts of the hint?" I think we can add some stuff to the book,
like text telling users it's a good idea to check Makefiles for every
command that installs something (grep "install" Makefile...or even add a
short script to the book that will output all that info...or
something...), without actually using the package user (which should
stay a hint).
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page