On Tue, 22 Nov 2005 13:33:44 -0600, David Masover <[EMAIL PROTECTED]> said:
> michael chang wrote: >> or to actually put package building scripts for package-handling >> distros in the source package (or use something like checkinstall, >> provided it doesn't conflict too bad). [You can also did what Debian >> did with it's 'kernel-package' system; it provides a package >> specially designed for converting a custom kernel into a package, > I think that's overkill, unless Debian really has no way to "provide" > or "inject" a particular package. Debian has a package called "equivs" that allows you to create dummy packages. But it is generally better to just include a debian/ directory in the sources, and let the Debian package management just handle everything for you (e.g. upgrading to a new version when Debian includes a newer version). Debian generally frowns upon including a debian/ directory in the upstream sources without any good reason. But I think that in this case, there is a good reason. Just make sure to work with the Debian maintainer of reiser4progs (Ed Boraas) if you want to do that. -- Hubert Chan <[EMAIL PROTECTED]> - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
