Thanks DJ, On Wed, Jul 28, 2010 at 3:19 AM, DJ Lucas <d...@linuxfromscratch.org> wrote:
> The problem with package management is that one flavor or the other is > not perfect for everyone. I personally prefer a simple tar.gz package Since, as Bruce and others mentioned, package management is not necessary for the LFS system learning experience, anyone who doesn't like it can just skip it. The reason I would like some PM system is to make it easier for users to experiment before writing their own automation and package management systems. For this purpose, the simpler the better. > for the users that like simple file lists. Here was the POC of Chapter > 6 at the time, just the installation scripts, which are more than a > little stale, but could be easily adapted for 6.6. > > http://www.linuxfromscratch.org/~dj/DESTDIR-LFS-6.4/ Thanks. I'll look at them. > Others who already use RPM, have also duplicated the same work as the > above, well before I did it, but the intention was to find a working > middle ground for use in the book. Could even take it a step further > and include the breaking up of bin, lib, and dev packages. Then it'd be > a cake walk to copy and past into your deb-build, or spec, or whatever > you can dream up. > >> >>>> 4. Include several BLFS installation paths up to date. > > I'm not sure I understand that request. I've taken it to mean a linear > BLFS. Is that what you meant? I'm afraid that the scope is far too Not all of BLFS. Just specific paths, for instance the host requirements for building LFS. > those tracking items. Shooting from the hip here, one easy way I can > think of would be to use specially formatted comment blocks, and a tool > to pre-process the xml source before handing over to the tools to > generate the completed book which would then be used by jhalfs. In That's something worth thinking about. > But, if I've understood the request correctly, you are asking for > something to be done when we are already taxed for editors. The only > way it will get done is if you, or somebody else, takes the lead and > runs with it...give us a small, but working POC to get all googly eyed Not at all. I was suggesting tasks which the book could use in the future. The only thing I requested at the moment is was to gage interest in such direction. I have been thinking in the past about working on automation/PM, but got the impression that no one was interested in any additions of this type to the book. --yaacov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
