Tushar Teredesai wrote these words on 01/15/06 23:28 CST: > The package version is 1.7. The -5 is debian's current patch level on > top of the released 1.7 version.
(Adding the following as additional information to this thread. In summary, I suggested that we simply pull out the changes to the popt.c file from the Debian package and package it as a BLFS patch, and go back to the 1.7 tarball with a BLFS patch) -------- Original Message -------- Subject: More popt Date: Sun, 23 Jan 2005 01:24:36 -0600 From: Randy McMurchy <[EMAIL PROTECTED]> To: Bruce Dubbs <[EMAIL PROTECTED]> Here's output from applying the debian patch to the 1.7 version of popt. Note that only 1 file is really modified that affects LFS. [snip] Only the popt.c file is changed that affects us. Everything else is Debian specific, or having to do with the autotools. And if you look at the mods to popt.c, they're trivial. They probably don't add anything that affects LFS (I could be wrong). [snip] It simply adds a couple of if statements to fix a failure on "funky platforms". I'm not sure that there's really anything in that whole patch that does a thing for us. However, if we want to use the trivial change to the popt.c file, I think we should pull out that change only (just the change to the popt.c file) and package that as a BLFS patch. And then go back to the original 1.7 version with a patch. What do you think? My feeling is that whole patch (and version increment to the package) is nothing but a bunch of fluff. -- 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] 07:46:00 up 113 days, 17:10, 3 users, load average: 0.14, 0.19, 0.21 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
