Dan Nicholson wrote these words on 02/16/07 18:37 CST: > On 2/16/07, BLFS Trac <[EMAIL PROTECTED]> wrote: >> Updated BLFS to PCI Utilities-2.2.4. Also added a note about linking >> the Zlib library to packages that may need to link to libpci.a. > > Randy, I don't know if this is a good idea yet. This will cause > problems with HAL because it doesn't use libpci. It just opens up > pci.ids and will have totally ignore pci.ids.gz. On the other hand, > update-pciids will always gzip the data if you built against zlib. > > So, in the best case, you have an old pci.ids hanging around that HAL > is going to use. In the worst case, you only have pci.ids.gz and HAL > will bomb.
Good point. However, going on your previous message about Python, it somewhat gives conflicting statements. On Python, you say, "Let's just see what breaks and have users report problems", with PCI Utils (a very minor program with really no impact on any other package but perhaps HAL), you say, "Oh, let's be careful". We can't have it both ways. I don't believe we have the manpower nor the time to discuss every single package update, especially one as trivial as PCI Utilities. If HAL needs it so badly, I'm sure it will fix itself to work with the .gz file and have an update soon. If not, we (BLFS people) will have to fix it. Please, don't construe this message as a gig against your idea. I'm only stating that I don't want to stifle development. If HAL is *completely broken* because of this update, all we need to do is in the HAL or PCI Utils instructions is mention that unzipping the file may be necessary. Seems a trivial fix. -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 22:05:02 up 37 days, 22:19, 1 user, load average: 0.43, 0.50, 0.46 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
