I'm going to write a program to automatically identify out of date packages for LFS. Has anyone already done such a beast?
As I review the packages, it seems that the only constant is inconsistency. Trying to parse versions is quite package specific. Packages may have versions with a single number (systemd, kbd, less), two numbers (vim, psmisc, etc), three numbers (most), and even four numbers (shadow). In one case, the version has a letter (tzdata). Some packages change the version scheme depending on release (util-linux-2.22.1 vs util-linux-2.23, gcc, linux kernel, etc. ) In addition, some directories that contain the packages vary with version (e.g. v2.23/util-linux..., check/0.9.10/..., gmp-5.1.1/..., 1.0.6/bzip..., mpfr-3.1.2/... ). Some sites don't allow a directory of the parent location so other means of determining the most recent version are needed (e.g. bzip2). Some directories change infrequently (kernel v3.x, 5.0/perl...) Sourceforge is generally a PITA because they do a lot of redirection which changes with version (prdownloads.sourceforge.net vs sourceforge.net/projects etc). When parsing a package filename for version, some packages have version numbers embedded (bzip2, iproute2, tcl8, e2fsprogs, expect5). Some package names have dashes (man-db, pkg-config, procps-ng, iana-etc). Writing a script to do all this is not particularly hard, but just long and tedious. There are some common elements in most of the packages from ftp.gnu.org. Has anyone else looked at this? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
