Tushar Teredesai wrote: > On Wed, Jul 3, 2013 at 11:10 PM, Bruce Dubbs <bruce.du...@gmail.com> wrote: > >> One of the more difficult things that I've found about BLFS is to >> determine whether a package in the book is current or not. I've >> decided to work on a set of scripts to help with that. >> > > Hi: > > I had taken a simplistic approach to this which did generate false > positives but never false negatives. I used to store the URI of the > download location for each package which could be a link to the directory > where the new versions are uploaded by the maintainer (e.g. > http://ftp.gnu.org/gnu/bash/) or a link to the latest file (e.g. > http://ftp.gnu.org/gnu/bash/bash-current.tar.gz). I used to store the > md5sum on each retrieval and compare it with the previously stored one. A > change would mean a possibility of update. Very few packages generated > false positives which I used to handle separately. > > I also think there is a package in gentoo which tries to parse the download > locations and figure out if there is an update.
Nice to hear from you again Tushar. I am parsing the download locations. It's just hard. When the location is ftp://ftp.gnome.org/pub/gnome/sources/glib/2.36, how do I know if the most recent is 2.36.3 or 2.38.0? I have to skip 3.27.x. It's not hard to see, but difficult to script. Other examples are a lot easier. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
