On Fri, Aug 27, 1999 at 01:52:47AM -0500, Brad wrote:
> On Fri, 27 Aug 1999, Matthew Dalton wrote:
> > Most packages, when compiled from source, will install their libraries
> > and executables in /usr/local somewhere, which is okay because dpkg
> > shouldn't touch that area. It must be possible though to put them all in
> > a .deb file so that you can remove/reinstall them easily later?
As well as producing .debs you might want to take a look at things like
GNU stow (avalible as a package) which provide much less managed package
management - basically, you install each program into a seperate tree and
use stow to symlink it into /usr/local.
> Read http://www.debian.org/doc/maint-guide/ to learn how to do it
> properly. There's a few steps in there that you can't do as a
> non-maintainer (e.g. uploading to master), but you will end up with a
> perfectly valid deb.
With tools like debmake and debhelper this can be a very simple thing to
do - there is some tutorial material avalible from
http://www.debian.org/devel/ and in the relevant packages.
> If you actually want to become a developer, read
> http://www.debian.org/doc/packaging-manuals/developers-reference/
If your package could be used by other people, this would probably be a
good thing to do - if you don't have time to maintain them, then you
could always offer them to someone else to maintain.
--
Mark Brown mailto:broonie@tardis.ed.ac.uk (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFS http://www.eusa.ed.ac.uk/societies/filmsoc/
Attachment:
pgpbIQyTI4e47.pgp
Description: PGP signature