version 1.32, 2000/06/15 16:48:50 |
version 1.33, 2000/06/17 15:13:00 |
|
|
|
|
<p> |
<p> |
<strong><font color=#e00000> |
<strong><font color=#e00000> |
Packages look like simple <code>.tar.gz</code> bundles, but they should always |
Packages look like simple <code>.tar.gz</code> bundles, but they should |
be added using pkg_add(1), as there might be some extra information that only |
always be added using |
pkg_add(1) knows how to handle.</font></strong> |
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>, |
Tip: you can distinguish between packages and .tar.gz bundles using pkg_info(1). |
as there might be some extra information that only |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a> |
|
knows how to handle.</font></strong> |
|
Tip: you can distinguish between packages and <strong>.tar.gz</strong> bundles |
|
using |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&sektion=1&format=html">pkg_info(1)</a>. |
|
|
<h3><font color=#0000e0>Getting packages</font></h3> |
<h3><font color=#0000e0>Getting packages</font></h3> |
|
|
|
|
|
|
<pre> |
<pre> |
# setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/i386/ |
# setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/i386/ |
# pkg_add gimp-1.17.tar.gz |
# pkg_add gimp-1.1.17.tar.gz |
</pre> |
</pre> |
|
|
<h3><font color=#0000e0>Managing installed packages</font></h3> |
<h3><font color=#0000e0>Managing installed packages</font></h3> |
|
|
The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a>. |
The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a> |
manual page holds useful information about ways to manage |
manual page holds useful information about ways to manage |
installed packages, solve conflicts (files that already exist) and handle |
installed packages, solve conflicts (files that already exist) and handle |
dependencies. |
dependencies. |
<p> |
<p> |
As of OpenBSD 2.7, to update a package you must: |
As of OpenBSD 2.7, to update a package you must: |
<ul> |
<ul> |
<li>Remove the old package using pkg_delete(1) |
<li>Remove the old package using |
<li>Add the new package using pkg_add(1) |
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_delete&sektion=1&format=html">pkg_delete(1)</a> |
|
<li>Add the new package using |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a> |
</ul> |
</ul> |
This is slightly inconvenient, as packages may trigger dependencies, and |
This is slightly inconvenient, as packages may trigger dependencies, and |
you may have to remove a large subset of packages for an update. |
you may have to remove a large subset of packages for an update. |
|
|
and recompile vast portions of the ports tree. |
and recompile vast portions of the ports tree. |
It is strongly suggested that people don't track ports-current unless |
It is strongly suggested that people don't track ports-current unless |
they're prepared to deal with various problems. |
they're prepared to deal with various problems. |
<a href=mail.html>Mailing lists</a> such as source-changes or tech will |
<a href=mail.html>Mailing lists</a> such as |
probably be invaluable. |
<code>source-changes@openbsd.org</code> or |
|
<code>tech@openbsd.org</code> will probably be invaluable. |
|
|
<p> |
<p> |
The ports-current tree can be retrieved via: |
The ports-current tree can be retrieved via: |
|
|
|
|
<p> |
<p> |
Let's say you managed to get a ports tree and you want to compile and |
Let's say you managed to get a ports tree and you want to compile and |
install the archiving utility <code>unzip</code>. You should be able to |
install the archiving utility <strong>unzip</strong>. You should be able to |
do something like this: |
do something like this: |
|
|
<pre> |
<pre> |