Timothy Rice wrote: > I was contemplating how to implement dependency tracking in the > Package User system and had an idea. Perhaps it would be of interest. > > <...> > > Opinions? Are there any obvious problems that I might have > overlooked?
How do you propose, during package X's installation, to find which other packages it depends on? It seems like that's a much bigger issue than how to encode the dependencies. Do you propose to make this part of the base package user hint, required for everyone, or some kind of optional addon? As a user of that hint, I'd rather you didn't bake it into the base set of assumptions it makes. (The only thing I think that hint needs -- for me -- is a way to restart a package's compilation in the middle. So I added an argument to my local package users' "build" scripts, that specifies which steps to run. Much more than that and it gets way too complicated for my tastes.)
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
