On 2/16/07, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Dan Nicholson wrote these words on 02/16/07 18:37 CST: > > > > 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".
That's understandable. But in the case of Python, I don't have any idea if things are broken and I think putting it in the book will help determine that. In the case of pciutils, I know something that it breaks. > 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. I suppose that's good enough. The problem really is that once you run update-pciids, it will automatically put in a new file that's zipped. So, if you have HAL, then you need to unzip it every time you do that. In which case, having zlib is useless. And, this isn't your fault, but if the pciutils developers want to make this feature supportable, they'd actually install their library that natively handles the proper file format instead of having others work around it. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
