On Friday 30 June 2006 19:37, Felipe Sateler wrote: > Joey Hess wrote: > > Maybe checkinstall could check to see if modules.dep is included and if > > so de-include it and the other files depmod touches, and add a proper > > call to depmod to the package's postinst script? This would make it > > really easy to make kernel module packages with it. > > I'm not really sure about this. Putting every possible case inside > checkinstall is not feasible. Also, checkinstall has a command line > option --exclude, which can be used to avoid the conflict. As for the > postinst, you can create a postinstall-pak file which will be appended to > the created package's postint script. I know it is a pain to have to do > this, but really think having checkinstall to remember every possible files > it should/shouldn't touch, procedures it has to do if certain files were > touched/commands executed it not the solution.
Upon further consideration, there is already a special case in checkinstall (libraries), and special cases don't seem to be that many anyways. So I'll try to implement this. However, I'm not familiar with how depmod works. AFAICS it touches the following files under /lib/modules/<version>/ modules.dep modules.pcimap modules.usbmap modules.ccwmap modules.ieee1394map modules.isapnpmap modules.inputmap modules.ofmap modules.seriomap modules.alias modules.symbols However, I can't be sure this are all the files it touches. Maybe under certain conditions it will touch other files as well. Also, this needs to be done as portable as possible. Are there any distributions that don't use this directory structure? I can't be certain about any of these things without extensive research, so any help is appreciated. -- Felipe Sateler
pgpWWQRNc36AV.pgp
Description: PGP signature
