El Domingo, 14 de Enero de 2007 07:56, Randy McMurchy escribió: > Bruce Dubbs wrote these words on 01/14/07 00:45 CST: > > I'm not sure, but that's not what I had in mind. > > > > 1. Parse the XML to get a list of all packages. > > 2. Compare the list to what we have. > > 3. Update the out of date packages. > > How does this account for changes in the subordinate downloads > of each and every package (the additional downloads in each > package, which are not annotated in general.ent, and only > identified in each package's XML)?
Yes, to can track also the additional or extra packages, if that is what we want, the full XML sources need be parsed. But that is also true for standard packages. general.ent alone isn't very useful due that some entities don't use the same package name that the one found in the tarball, there is a generic version value for several KDE and GNOME packages, and there is several version entities for additional Perl modules that don't have download links. We can try to create a framework to track packages updates, addition or removal, but I need to know what info must contains the generated file and in what format should be presented to be of some utility when updating the FTP server. Justin? PD: Backing to home after a log-long holidays travel I'm very happy to see that BLFS is on development again and that Alexander is now a BLFS editor. But I'm afraid about the lack of LFS updates :-/ -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
