Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 03-15-2007, 05:51 PM   #16
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Rep: Reputation: 30

Originally Posted by onebuck
READ the 'man removepkg'!
i have, but I still don't understand how this:
Originally Posted by man removepkg
removepkg removes a previously installed Slackware package,
affects non-Slackware packages, and even 3rd party packages (i.e. slackbuilds, checkinstall, compiled from source) it seems the 'packages' still show up in /var/log/packages no matter how I install them. By "Slackware package" does that include anything install-able with installpkg?

clearly there is more for me to read & learn.

also thanks for the 'dd' link, holy smokes thats a lot of info...
Old 03-16-2007, 04:38 AM   #17
Amigo developer
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,856

Rep: Reputation: 547Reputation: 547Reputation: 547Reputation: 547Reputation: 547Reputation: 547
Basically what distinguishes a Slackware package is that it contains an directory called /install which conatins at least a slack-desc file. When the package is installed using installpkg, the contents of this file get read and added to a database file which installpkg generates when lists the included files, etc. If you use installpkg on a non-Slackware tgz archive, the database file will still be generated in /var/log/packages, but maybe not correctly because of the missing slack-desc.
Installing software with 'make install' will not do this, so the installed files are not accounted for in the /var/log/packages database. Slackware-compatible package managesr won't be aware of the installed files. they can be searched out with an 'orphan' utility, but it will lump all non-recognized files together, without knowing what belongs to a particular installed program.
Slackbuilds, checkinstall, autoslack, src2pkg and others are all programs for creating packages which are compatible with installpkg and removepkg and construct the package accordingly.

As far as unpacking, installpkg just runs tar in the root directory and will work with any archive that ends in .tgz -even source packages or whatever. This is why it's not really a good idea to use installpkg to install rpm's which have been converted using rpm2tgz -these archives contain no slack-desc file, may have weird permissions or non-slackish directory structure, etc. But installpkg will unpack it on your system, regardless.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Desktop icons dosnt have ToolTips (apear when mouse hover above desktop icon) Acidx Linux - General 1 12-03-2006 07:48 PM
Partitioning advice for a desktop with a 80GB HD + 60GB HD Korto Linux - Newbie 7 08-23-2006 02:02 AM
Partitioning scheme for software devel workstation/desktop introuble Fedora 1 06-26-2006 10:34 AM
Partitioning for a Development Workstation / Desktop introuble Linux - General 2 06-15-2005 03:25 PM
Loss of desktop functionality after setting new desktop from firefox in fc2/gnome. dr_zayus69 Linux - Software 3 03-09-2005 09:29 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:38 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration