Sponsored Content
Full Discussion: removing package.
Top Forums UNIX for Advanced & Expert Users removing package. Post 44899 by jsilva on Friday 12th of December 2003 04:42:53 AM
Old 12-12-2003
Hi,

To remove a package, use pkg_delete... try to find the exact name of daemontools and do "pkg_delete daemontools-0.1" ( for example ).
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Removing a package in unix

I have a package that i'm going to be adding...i wanted to make sure i knew how to remove it prior to instalation.. expect-5.40-sol8-sparc-local.gz pkgadd -d ./expectpkg/ would the command to remove this package be... pkgrm expect-5.40-sol8-sparc-local or is the package instance not... (5 Replies)
Discussion started by: cubs0729
5 Replies

2. Linux

how to restore original package after uninstalling the upgraded package using rpm

have following package installed rpm -qa |grep ADMIN It will give the following package installed: ADMIN-4.0.0.1 Now I will upgrade the ADMIN package using the following command. rpm --upgrade ADMIN-4.1.0.1 It will upgrade the ADMIN packagge to ADMIN-4.1.0.1 Now I want that... (0 Replies)
Discussion started by: amitpansuria
0 Replies

3. Solaris

error in removing the package

hi all, i have installed gcc-3.4.6-sol10-sparc-local package on unix system. i tried removing this with the command pkgrm but getting the below error.. pkgrm gcc-3.4.6-sol10-sparc-local pkgrm: ERROR: no package associated with <gcc-3.4.6-sol10-sparc-local> can any one suggest me how... (2 Replies)
Discussion started by: ani_rvce
2 Replies

4. AIX

mkinstallp package creation failing "no such file: ./usr/lpp/<package name>/inst_root"

Hello, I'm trying to build a (bff) package from an already installed program (clam antivirus) using mkinstallp. However, mkinstallp fails with "no such file: ./usr/lpp/<package name>/inst_root" I'm not sure why all files get created ok except for these particular ones. Any help would be... (2 Replies)
Discussion started by: omonte
2 Replies

5. UNIX for Advanced & Expert Users

How to find dependancies of .dstream package (Solaris) & .rpm package( linux)

Friends, Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ? For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies

6. Linux

How install a new package without remove old package?

Dear all, I would like to install a new version of package without remove old version on Centos and vice versa. Please give me advice! thanks much, (2 Replies)
Discussion started by: all4cfa
2 Replies

7. UNIX for Dummies Questions & Answers

Can't install rpm package with --prefix in new path.Error: package is not relocatable

Hello, i have downloaded an rpm package "hadoop-0.20.205.0-1.amd64.rpm" in /usr/local/ directory. I'm trying to install the rpm package in a new path/location (/usr/local/hadoop-0.20.205), but i can't. I did: 1st try: Didn't work sudo rpm -i --prefix=/usr/local/hadoop-0.20.205... (1 Reply)
Discussion started by: g_p
1 Replies

8. Emergency UNIX and Linux Support

Problem when trying to remove a package using rpm command - error: package is not installed

Hello, i have installed a package by using the command sudo rpm -i filepackage.rpm package filepackage is already installed when i try to remove it, i get an error saying "is not installed": sudo rpm -e filepackage.rpm error: package filepackage is not installed How can... (4 Replies)
Discussion started by: g_p
4 Replies

9. UNIX for Dummies Questions & Answers

Removing PATTERN from txt without removing lines and general text formatting

Hi Everybody! First post! Totally noobie. I'm using the terminal to read a poorly formatted book. The text file contains, in the middle of paragraphs, hyphenation to split words that are supposed to be on multiple pages. It looks ve -- ry much like this. I was hoping to use grep -v " -- "... (5 Replies)
Discussion started by: AxeHandle
5 Replies
PKG_DELETE(1)						    BSD General Commands Manual 					     PKG_DELETE(1)

NAME
pkg_delete -- a utility for deleting previously installed software package distributions SYNOPSIS
pkg_delete [-ADFfkNnORrVv] [-K pkg_dbdir] [-P destdir] [-p prefix] pkg-name ... DESCRIPTION
The pkg_delete command is used to delete packages that have been previously installed with the pkg_add(1) command. The given packages are sorted, so that the dependencies needed by a package are deleted after the package. Before any action is executed, pkg_delete checks for packages that are marked as preserved or have depending packages left. If the -k flag is given, preserved packages are skipped and not removed. Unless the -f flag is given, pkg_delete stops on the first error. WARNING
Since the pkg_delete command may execute scripts or programs provided by a package file, your system may be susceptible to ``Trojan horses'' or other subtle attacks from miscreants who create dangerous package files. You are advised to verify the competence and identity of those who provide installable package files. For extra protection, examine all the package control files in the package record directory <PKG_DBDIR>/<pkg-name>/). Pay particular attention to any +INSTALL or +DEINSTALL files, and inspect the +CONTENTS file for @cwd, @mode (check for setuid), @dirrm, @exec, and @unexec directives, and/or use the pkg_info(1) command to examine the installed package control files. OPTIONS
The following command line options are supported: pkg-name ... The named packages are deinstalled, wildcards can be used, see pkg_info(1). If no version is given, the one currently installed will be removed. If the -F flag is given, one or more (absolute) filenames may be specified and the package database will be consulted for the package to which the given file belongs. These packages are then deinstalled. -A Recursively remove all automatically installed packages that were needed by the given packages and are no longer required. Does not remove manually installed packages; see also the -R flag. -D If a deinstallation script exists for a given package, do not execute it. -F Any pkg-name given will be interpreted as pathname which is subsequently transformed in a (real) package name via the package data- base. That way, packages can be deleted by giving a filename instead of the package-name. -f Force removal of the package, even if a dependency is recorded or the deinstall script fails. This might break the package database; see pkg_admin(1) on how to repair it. -ff Force removal of the package, even if the package is marked as a preserved package. Note that this is a dangerous operation. See also the -k option. -K pkg_dbdir Override the value of the PKG_DBDIR configuration option with the value pkg_dbdir. -k Silently skip all packages that are marked as preserved. -N Remove the package's registration and its entries from the package database, but leave the files installed. Don't run any deinstall scripts or @unexec lines either. -n Don't actually deinstall a package, just report the steps that would be taken. -O Only delete the package's entries from the package database; do not touch the package or its files itself. -P destdir Prefix all file and directory names with destdir. For packages without install scripts this has the same behavior as using chroot(8). -p prefix Set prefix as the directory in which to delete files from any installed packages which do not explicitly set theirs. For most pack- ages, the prefix will be set automatically to the installed location by pkg_add(1). -R Recursively remove all packages that were needed by the given packages and are no longer required. This option overrides the -A flag. -r Recursively remove all packages that require one of the packages given. -V Print version number and exit. -v Turn on verbose output. TECHNICAL DETAILS
pkg_delete does pretty much what it says. It examines installed package records in <PKG_DBDIR>/<pkg-name>, deletes the package contents, and finally removes the package records. If a package is required by other installed packages, pkg_delete will list those dependent packages and refuse to delete the package (unless the -f option is given). If a package has been marked as a preserved package, it will not be able to be deleted (unless more than one occurrence of the -f option is given). If a filename is given instead of a package name, the package of which the given file belongs to can be deleted if the -F flag is given. The filename needs to be absolute, see the output produced by the pkg_info(1) -aF command. If a deinstall script exists for the package, it is executed before and after any files are removed. It is this script's responsibility to clean up any additional messy details around the package's installation, since all pkg_delete knows how to do is delete the files created in the original distribution. The deinstall script is called as: deinstall <pkg-name> VIEW-DEINSTALL before removing the package from a view, and as: deinstall <pkg-name> DEINSTALL before deleting all files and as: deinstall <pkg-name> POST-DEINSTALL after deleting them. Passing the keywords VIEW-DEINSTALL, DEINSTALL, and POST-DEINSTALL lets you potentially write only one program/script that handles all aspects of installation and deletion. All scripts are called with the environment variable PKG_PREFIX set to the installation prefix (see the -p option above). This allows a package author to write a script that reliably performs some action on the directory where the package is installed, even if the user might have changed it by specifying the -p option when running pkg_delete or pkg_add(1). The scripts are also called with the PKG_METADATA_DIR environment variable set to the location of the +* meta-data files, and with the PKG_REFCOUNT_DBDIR environment variable set to the location of the package reference counts database directory. If the -P flag was given to pkg_delete, PKG_DESTDIR will be set to destdir. ENVIRONMENT
See pkg_install.conf(5) for options, that can also be specified using the environment. SEE ALSO
pkg_add(1), pkg_admin(1), pkg_create(1), pkg_info(1), pkg_install.conf(5) pkgsrc(7) AUTHORS
Jordan Hubbard most of the work John Kohl refined it for NetBSD Hubert Feyrer NetBSD wildcard dependency processing, pkgdb, recursive "down" delete, etc. Joerg Sonnenberger Rewrote most of the code to compute correct order of deinstallation and to improve error handling. BSD
January 20, 2010 BSD
All times are GMT -4. The time now is 09:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy