Tracking files of non rpm packages

Discuss Applications
Post Reply
User avatar
Calum
guru
guru
Posts: 1349
Joined: Fri Jan 10, 2003 11:32 am
Location: Bonny Scotland
Contact:

Tracking files of non rpm packages

Post by Calum » Sun Mar 23, 2003 10:06 am

hello.

what methods are there for tracking the files of packages that i install which are not rpms? as you know, not everything is available as an rpm and anyway, i want to use slackware so will likely want to keep track of more than one type of package on a regular basis.

Basically i want to know if there's an established way to keep track of what's been installed and how, for future uninstallation in as clean a way as possible. If i want to upgrade something or if i want to install something that depends on something else, i would like to make as little trouble for myself (and have as few conflicts) as possible. Some of the things i want to install are source code only, but if i use slackware, many packages will have been installed as pkgtool packages during system setup, and if i use red hat (which i currently do) then many will be rpm packages.

is it worth installing rpm in slackware or will this just confuse source packages that depend on rpms i have installed and vice versa?

what's the best way to manage the installation of packages in more than one format in your opinion?

Doogee
administrator
administrator
Posts: 261
Joined: Fri Jan 10, 2003 1:40 am

Post by Doogee » Mon Mar 24, 2003 1:37 am

slackware includes a tool set thing called pkgtool which uses slackware packages, which come in *.tgz form, although there not not regular tarballs, these are very easy to install/uninstall.

the easiest is probably the command "# pkgtool" which seems to infact track the way of slackpacks.

Slackpacks are the best to use with slack, but not easily found. I have usually been installing from source and im yet to find a good way of tracking them.

Nobber
user
user
Posts: 32
Joined: Thu Jan 23, 2003 8:36 am
Location: Slackville

Post by Nobber » Mon Mar 24, 2003 6:35 am

You can get some ideas on how to manage source installations from the LFS FAQ. I haven't used any of these schemes, though, so I can't recommend one over another.

User avatar
Calum
guru
guru
Posts: 1349
Joined: Fri Jan 10, 2003 11:32 am
Location: Bonny Scotland
Contact:

Post by Calum » Mon Mar 24, 2003 7:00 am

good link, nobber, i thought about CVS (which i completely do not understand) but it looks like it is not for dialup users like me, or for just any old source packages either.

i hope to install slackpackages but then to install source packages afterwards and i am thinking even of trying to put rpm on there (but will this be a headache because the rpm database will not record glibc6 and so on?)

Post Reply