dpkg and /usr/local packages
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Problem: when I install some package from source (like Emacs, or GTK
et al), dpkg doesn't know about these... which means that I
cannot install any package that depends on this (not without
forcing the dependencies).
Solution A: how about some <package>-upstream package, similar to the
(wonderful! Thanks, Brian!) netscape4 package. This
package would create an environment like the corresponding
<package> package, but using the locally installed
components for this.
Yes, I know this is more work for the maintainers...
though I don't think it would be too much.
Solution B: Give dpkg a --force-known option, which causes the
specified package to be known as installed.
Now document the differences (in installation) between a
standard source install (w/o any --prefix magic) and the
Debian install of said package, and leave it to the local
admin to sync both.
More (though most of the time not much) work for the local
admin, almost none for the package maintainer.
Plan B is similar in function to the equivs package... what the equivs
package lacks (apart from being an ugly, ugly, *ugly* hack) is the
documentation of then differences between a source install and a
debian package.
For example, I would have used equivs on Emacs, but I'm not sure what
to do about the emacsen-common package... does it work to simple
install emacsen-common, followed by emacs20 (using equivs)? Or do I
even need emacsen-common? But maybe I'm just too dumb for this
shit... ;-)
Anyway,
Bye, J
- --
Jürgen A. Erhard eMail: jae@ilk.de phone: (GERMANY) 0721 27326
My WebHome: http://members.tripod.com/~Juergen_Erhard
George Herrimann's Krazy Kat (http://www.krazy.com)
Win32 has many known work arounds. For example, Linux.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.0 (GNU/Linux)
Comment: For info see www.gnupg.org
iEYEARECAAYFAjaU6XMACgkQ+EdE6uFQHp+d8wCdFtUx9JlI4ErpBZ5HbZH/MfX1
jSIAoKyP+eHrHpcfvfekLrMiO6LRGwM5
=/9TJ
-----END PGP SIGNATURE-----
Reply to: