We are still actively working on the spam issue.

Difference between revisions of "Package manager"

From InstallGentoo Wiki
Jump to: navigation, search
(more info on non-looonix package maintainers)
Line 176: Line 176:
  
 
Speaks for itself (replace ''packagename'' with your actual package name obviously):
 
Speaks for itself (replace ''packagename'' with your actual package name obviously):
 +
 
<code>pkg install ''packagename''</code>
 
<code>pkg install ''packagename''</code>
 +
 
<code>pkg delete ''packagename''</code>
 
<code>pkg delete ''packagename''</code>
 +
 
<code>pkg info ''packagename''</code>
 
<code>pkg info ''packagename''</code>
 +
 
<code>pkg search ''packagename''</code>
 
<code>pkg search ''packagename''</code>
 +
 
<code>pkg upgrade</code>
 
<code>pkg upgrade</code>
 +
 
<code>pkg autoremove</code>
 
<code>pkg autoremove</code>
  
Line 186: Line 192:
  
 
<code>pkg_add ''packagename''</code>
 
<code>pkg_add ''packagename''</code>
 +
 
<code>pkg_delete ''packagename''</code>
 
<code>pkg_delete ''packagename''</code>
 +
 
<code>pkg_info ''packagename''</code>
 
<code>pkg_info ''packagename''</code>
 +
 
<code>pkg_add -u ''packagename''</code> to upgrade ''packagename'' -- if you don't supply a ''packagename'' it will upgrade everything
 
<code>pkg_add -u ''packagename''</code> to upgrade ''packagename'' -- if you don't supply a ''packagename'' it will upgrade everything
  
Line 193: Line 202:
  
 
To use the ports system, simply go to your desired port' directory (usually found in /usr/ports/) and compile it. For instance, if you want to install qTox:
 
To use the ports system, simply go to your desired port' directory (usually found in /usr/ports/) and compile it. For instance, if you want to install qTox:
 +
 
<code>cd /usr/ports/net-im/qTox</code>
 
<code>cd /usr/ports/net-im/qTox</code>
 +
 
<code>make install clean</code>
 
<code>make install clean</code>
  
Line 209: Line 220:
 
== brew ==
 
== brew ==
 
<code>brew install ''formula''</code>
 
<code>brew install ''formula''</code>
 +
 
<code>brew uninstall ''formula''</code>
 
<code>brew uninstall ''formula''</code>
 +
 
<code>brew tap ''repo''</code>
 
<code>brew tap ''repo''</code>
 +
 
<code>brew update</code>
 
<code>brew update</code>
 +
 
<code>brew upgrade</code>
 
<code>brew upgrade</code>
 +
 
<code>brew help</code>
 
<code>brew help</code>
  
 
[[Category:GNU/Linux]]
 
[[Category:GNU/Linux]]
 
[[Category:Package manager]]
 
[[Category:Package manager]]

Revision as of 14:47, 12 February 2015

Cleanup.png
Cleanup.png
CLEANUP CANDIDATE
Relevant discussion may be found on the talk page. Reason: No reason specified.


This is the software repositories that you will meet with some *nix os. They are used to download your software in opposition to compiling them from source. In other words they automatate every thing for the dumb shit you are and allow you to install, update and remove the application you need cause youre to retarded to write them by yourself with a magnifying glass and the sun directly on your hard drive. The most common package managers are yum (RHEL - rpm) and apt (Debian - deb).

GNU/Linux

apt

You run it like this:

To install: sudo apt-get install <package>

To update the package list: sudo apt-get update

To upgrade exsiting package: sudo apt-get upgrade

To remove: sudo apt-get remove <package>

To clean: sudo apt-get clean <package>

To search for a package with <package> in its name or "Provides" list: apt-cache search --names-only <package>

To search for a package with <query> in its description: apt-cache search <query>

To get build dependencies for <package>: sudo apt-get build-dep <package>

To remove unneeded dependencies: sudo apt-get autoremove

yum

See the yum page.

Zypper

Zypper is a cli frontend for openSUSEs package manager, libzypp. The .rpm package format is used, but the package manager itself is independent from RHEL.

In contrast to most other package managers, zypper does not require the user to update the repository listings manually. the 'update' funcion actually updates the system ( in other words, it does what other package managers refer to as 'upgrading')

usage:

zypper in <name of package>

zypper rm <name of package>

installs or removes a package

zypper ar <repo>

zypper rr <repo>

adds or removes a repository

zypper up updates

zypper se <name of package> searches

original forms can be used instead of short forms:

  • se = search
  • up = update
  • in = install
  • etc.

portage

sync:

emerge --sync

search:

emerge --search <variable>

search description:

emerge --searchdesc <variable>

install:

emerge <variable>

uninstall:

emerge --unmerge <variable>

pretend install:

emerge --pretend <variable>

fetch source only:

emerge --fetchonly <variable>

check USE flags:

emerge -vp <variable>

full system update:

emerge --update --deep --with-bdeps=y --newuse @world

slackpkg

Slackpkg is Slackware's package manager.

Install a package

slackpkg install PACKAGE

Remove a package

slackpkg remove PACKAGE

Search for a package

slackpkg search PACKAGE

Upgrade a package

slackpkg upgrade PACKAGE

Update the repository listings

slackpkg update

Get information on a package

slackpkg info PACKAGE

Update all packages

slackpkg upgrade-all


Unofficial packages

The slackpkg repositories are limited to Slackware core packages. Unofficial packages can be downloaded and added with

upgradepkg --install-new FILENAME

Slackware also supports building packages from source code or .rpm files with Slackbuild scripts. This gives the security and flexibility of building from source with the ease of package-based management.

Download and extract the Slackbuild tarball

Download the source tarball/.rpm file and place it in the Slackbuild directory

cd into the slackbuild directory

OPTIONAL: Edit the configuration file if one exists and you so desire

Run the PROGRAM_NAME.Slackbuild script

sudo bash PROGRAM_NAME.Slackbuild

After the script finishes, the last line should read "Package /tmp/PACKAGE_NAME.tgz successfuly created" (Or lots of errors, especially if you forgot the sudo)

Install the package

sudo upgradepkg --install-new /tmp/PACKAGE_NAME.tgz


Enjoy your overflowing abundance of freedom and simplicity


pacman

See the pacman page.

*BSD

There are two main ways to install software on *BSDs: through binaries (pkg) or compiled sources (ports)

pkg

FreeBSD

Speaks for itself (replace packagename with your actual package name obviously):

pkg install packagename

pkg delete packagename

pkg info packagename

pkg search packagename

pkg upgrade

pkg autoremove

OpenBSD

pkg_add packagename

pkg_delete packagename

pkg_info packagename

pkg_add -u packagename to upgrade packagename -- if you don't supply a packagename it will upgrade everything

ports

To use the ports system, simply go to your desired port' directory (usually found in /usr/ports/) and compile it. For instance, if you want to install qTox:

cd /usr/ports/net-im/qTox

make install clean

OS X

On top of the App Store and the Hack Store, OS X comes with third-party package managers.

fink

See the main page.

macports

See the main page.

brew

brew install formula

brew uninstall formula

brew tap repo

brew update

brew upgrade

brew help