Re: howto manage programs compiled from source ???
On 07-Jun-2002 Michael D. Schleif wrote: Where is some howto explaining ins and outs and options to managing programs compiled from source under debian? Clearly, one reason to choose debian is apt/dpkg/dselect, et al. However, as we know, some programs may have to be compiled from source. It is also clear to me that such self compiled programs are not known to the package management databases and, therefore, are susceptible to being broken by subsequent package manager installations, c. So, I am wondering whether or not there is some best practices already written to address these concerns. What do you think? there are two groups of sources: packaged sources you compile and unpackaged. The first case is fairly easy, you apt-get source the package, compile it and place it on hold. It is the second case that can get ugly. The easiest solution is to install everything not from a Debian package into /usr/local or maybe /opt. The Debian package system ignores these two hierarchies. The problems arise when you have a package in Debian which needs a package that you installed by source and thus have no way to satisfy the depends. At this point you can either make a dummy package to appease dpkg or look into the 'equivs' package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: howto manage programs compiled from source ???
Michael D. Schleif [EMAIL PROTECTED] writes: Where is some howto explaining ins and outs and options to managing programs compiled from source under debian? I'm not sure if there's any concise documentation out there, but... Clearly, one reason to choose debian is apt/dpkg/dselect, et al. However, as we know, some programs may have to be compiled from source. It is also clear to me that such self compiled programs are not known to the package management databases and, therefore, are susceptible to being broken by subsequent package manager installations, c. If you install things under /usr/local, you get a guarantee that dpkg won't touch them; the only things allowed to be installed there are empty directories. You might also consider using the 'equivs' package to lie to dpkg about what's installed, if you consider this necessary. The 'stow' package can be useful for organizing /usr/local, if you have lots of things installed there. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: howto manage programs compiled from source ???
Michael == Michael D Schleif [EMAIL PROTECTED] writes: [...] Michael It is also clear to me that such self compiled programs are not Michael known to the package management databases and, therefore, are Michael susceptible to being broken by subsequent package manager Michael installations, c. User compiled programs should be stuffed into /usr/local (or some similar area), which the package manager shouldn't touch (much). It may also be worth looking into the stow package: , | Package: stow | ... | Description: Organiser for /usr/local/ hierarchy | GNU Stow helps the system administrator organise files under /usr/local/ | by allowing each piece of software to be installed in its own tree under | /usr/local/stow/, and then using symlinks to create the illusion that | all the software is installed in the same place. ` -- 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. pgptoQk8pDBlD.pgp Description: PGP signature
