> Date: Fri, 15 Nov 2013 09:39:06 -0600 > From: Bruce Dubbs <bruce.du...@gmail.com> > To: BLFS Development List <blfs-dev@linuxfromscratch.org> > Subject: Re: [blfs-dev] Proposed changes > > akhiezer wrote: > >> Date: Fri, 18 Oct 2013 12:12:16 -0500 > >> From: Bruce Dubbs <bruce.du...@gmail.com> > >> To: BLFS Development List <blfs-dev@linuxfromscratch.org> > >> Subject: Re: [blfs-dev] Proposed changes > >> > > . > > . > >> > >>>> Remove printproto and libXp since they are basically unused. > >>> > >>> Like Nathan, I thought these were for something in the open jdk > >>> area. > >> > >> I can't find any reference to printproto in any jdk file or log. I > >> found one mention of libXp in the INSTALL text file of IcedTea, but I > >> don't see where it is ever used. > >> > > > > > > blfs74 states quite clearly on libXp page that 'printproto' is a required > > dep. > > (Whether that's really true or not is a different matter: there's quite a > > lot > > of inaccuracies in the deps sections in blfs.) > > > > blfs74 also states quite clearly on both libXp and printproto pages, that > > each > > is used for testing that X install is OK. (Again, whether that's actually > > true > > or not, ... .) > > > > I see though that both are already out of svn. Are the X tests, at least, > > that > > use libXp/printproto, considered not relevant or worth doing? > > > > (More generally, what the 'Proposed changes' and 'Discussion about archiving > > more GNOME packages' threads from Oct/Nov, flag up again is that handling of > > deps-trees is still not very rigourous or automated in blfs.) > > Dependencies are definitely not automated. How would you do that? >
I mean parsing of the blfs xml tree to build a deps-tree: but that of course still depends on accuracy of info in said tree; and given current & ongoing inaccuracies, said parser still needs some 'overrides' that augments/ corrects-for the xml input. Was not meaning (full) auto-extraction from source-packages. (( Although there are some inklings of such formal structure specs starting to be included in some source packages, it's still early days (& there'll, if ever, likely be the usual 15 different 'standards'). In the meantime, for packages with 'configure --help', auto-parsing that can be a good start and cross-check; but of course still needs augmented with the still-usual other sources of info - e.g. package README, INSTALL, &c, plus user experience, bug-reports, etc. )) akh -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
