Hi Bryan, > 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.
You are correct. At this stage, I am manually putting the list of dependencies into a text file. The process of dependency-determination can (and will) eventually be automated, by having a script or program that scans the book's source code for dependencies. However, that sort of thing is a bit out of my league at the moment. You'll just have to be patient. > 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. Well, what I propose is that it ***could*** be "baked into" the hint. What I am **not** doing is attempting to dictate what "should" happen. I am just submitting an idea for consideration. It will be accepted or rejected. Most likely the latter. That's okay. I would still like to discuss the strengths and weaknesses of the idea anyway. > (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.) Then I would not suggest that you take up my idea... Cheers, Tim -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
