Re: Maintaining the operating environment Questions:
On Fri, Jul 31, 1998 at 11:01:54AM -0400, Will Lowe wrote: > On Fri, 31 Jul 1998, G. Kaplan wrote: > > > 3. a primary module i.e. .xyz.tar.gz > Generally it's safest to untar, compile and install these with > prefix=/usr/local ... debian packages won't touch anything under > /usr/local, so nothing will get overwritten or anything. In general, a > lot of stuff you compile from tarballs yourself has a default install > under /usr/local. With respect to 1. and 2., one has to be careful here. Native Debian packages don't touch /usr/local, so it is safe to put local add ons there (and this is the intended and formal correct place). BUT inofficial *.deb files and *.rpm files converted with alien may very well contain /usr/local files, please check this with the "--contents" option prior installation. I believe you can even convert tar files to deb files. This is intereting if you want to make /usr/local managed by dpkg. Thank you, Marcus -- "Rhubarb is no Egyptian god."Debian GNU/Linuxfinger brinkmd@ Marcus Brinkmann http://www.debian.orgmaster.debian.org [EMAIL PROTECTED]for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Maintaining the operating environment Questions:
On Fri, 31 Jul 1998, G. Kaplan wrote: > Is there any way to determine the distribution source of an installed > module ? Not sure what you're asking here. > Suppose I wanted to maintain a system through dpkg , where is it > reasonable to store files that are not part of the current standard > distribution; but are: > 1. a properly defined .deb package, These can be handled by dpkg -- even if they're not in the "current distribution", it'll install them and keep track of them for you. It'll mark them as Obselete/Local in its package listing (because they don't fit in its current notion of what the distribution is, but otherwise with no side effects), but won't complain about installing or managing them for you. > 2. a properly defined .rpm package Use "alien" to convert it to a .deb and then see #1. > 3. a primary module i.e. .xyz.tar.gz Generally it's safest to untar, compile and install these with prefix=/usr/local ... debian packages won't touch anything under /usr/local, so nothing will get overwritten or anything. In general, a lot of stuff you compile from tarballs yourself has a default install under /usr/local. Will -- | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | | http://www.cis.udel.edu/~lowe/ | |PGP Public Key: http://www.cis.udel.edu/~lowe/index.html#pgpkey| -- |And if you on tight to what you think is your thing | |you may find you're missing all the rest ...| |- Dave Matthews, "Best of What's Around" | -- -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Maintaining the operating environment Questions:
Is there any way to determine the distribution source of an installed module ? Suppose I wanted to maintain a system through dpkg , where is it reasonable to store files that are not part of the current standard distribution; but are: 1. a properly defined .deb package, 2. a properly defined .rpm package, or 3. a primary module i.e.. xyz.tar.gz What are the consequences with respect to 'Packages' , 'available', 'available-old', 'status', 'status-old'? What side effects should I be on the look out for? I am reading the programmer and policy documentation; but do not feel comfortable with my lack of understanding of side effects. Thank you. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
