Re: How to ensure packages generated from -source are installable?

2005-01-14 Thread Goswin von Brederlow
William Ballard [EMAIL PROTECTED] writes: On Mon, Jan 03, 2005 at 11:33:21AM +0100, Thomas Hood wrote: Right. Do you regard this as a problem? It would be a lot smarter to check if the install would succeed before unpacking it. If you were replacing a previous alsa-modules package, the

Re: How to ensure packages generated from -source are installable?

2005-01-03 Thread Thomas Hood
On Sun, 02 Jan 2005 04:20:04 +0100, William Ballard wrote: Kernel module source packages generated Debian packages which may not be installable. For instance, alsa-source does not depend on alsa-base, but the generated alsa-modules does. ndiswrapper-source does the same with

Re: How to ensure packages generated from -source are installable?

2005-01-03 Thread Jose Carlos Garcia Sogo
El lun, 03-01-2005 a las 11:33 +0100, Thomas Hood escribi: [...] What ends up happening now is the package ends up installing broken. I am not sure what you mean by this. Here is what happens when I install an alsa-modules package in the absence of alsa-base: [EMAIL

Re: How to ensure packages generated from -source are installable?

2005-01-03 Thread William Ballard
On Mon, Jan 03, 2005 at 11:33:21AM +0100, Thomas Hood wrote: Right. Do you regard this as a problem? It would be a lot smarter to check if the install would succeed before unpacking it. If you were replacing a previous alsa-modules package, the old one will be uninstalled and non-functional

How to ensure packages generated from -source are installable?

2005-01-01 Thread William Ballard
Kernel module source packages generated Debian packages which may not be installable. For instance, alsa-source does not depend on alsa-base, but the generated alsa-modules does. ndiswrapper-source does the same with ndiswrapper-utils. Is there a flag to dpkg to refuse to install unless