Tushar Teredesai wrote these words on 08/04/05 17:59 CST: > I would like to propose that before adding/removing packages from the > book, we should formalize what packages can be included in the book > (Jeroen had already started the process of formalizing the process > before he left, maybe that should be revived). After formalizing, a > decision can be made whether the current packages fit that criteria or > not and then decide whether any new packages that are suggested fit in > that criteria. Of course there will always be exceptions to the rule
A noble thought. However, it appears that this idea has been encountered before (years ago?) and nothing has been done about it. I'm not so sure that a policy (which you are proposing) that requires something that has been kicked around now for many, many months (at least) and nothing has ever been done about, is a good thing. In the meantime, your proposal stagnates any new consideration of other packages. Perhaps if such a document was formalized, then your idea would be very valuable. Reference the document, if it fits - do it, if not - don't. However, LFS history has shown that we cannot count on such a document to become formalized. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 18:06:01 up 124 days, 17:39, 2 users, load average: 1.07, 0.78, 0.39 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
