From 7e1b7fd9a3252a1e717b50670c006e068a6bd4bc Mon Sep 17 00:00:00 2001 From: rillig Date: Sat, 29 Jul 2006 14:14:23 +0000 Subject: Integrated the useful information from the NetBSD guide, chap-pack.xml, where the pkgsrc guide did not mention things before. Discarded the rest. --- doc/guide/files/getting.xml | 11 +++++++-- doc/guide/files/submit.xml | 6 +++-- doc/guide/files/using.xml | 60 +++++++++++++++++++++++++++++++++++++++------ 3 files changed, 65 insertions(+), 12 deletions(-) (limited to 'doc/guide') diff --git a/doc/guide/files/getting.xml b/doc/guide/files/getting.xml index 887745e2f59..4b739518476 100644 --- a/doc/guide/files/getting.xml +++ b/doc/guide/files/getting.xml @@ -1,4 +1,4 @@ - + Where to get pkgsrc and how to keep it up-to-date @@ -121,7 +121,14 @@ When removing the old files, any changes that you have done to the pkgsrc files will be lost after updating. Therefore updating via CVS is strongly recommended. - + + Note that by default the distfiles and the binary packages + are saved in the pkgsrc tree, so don't forget to rescue them + before updating. You can also configure pkgsrc to use other than + the default directories by setting the + DISTDIR and PACKAGES + variables. See for the details. + To update pkgsrc from a tar file, download the tar file as explained above. Then, make sure that you have not made any changes to the files in the pkgsrc directory. Remove the pkgsrc diff --git a/doc/guide/files/submit.xml b/doc/guide/files/submit.xml index 68b825a156b..1fc57a7ba02 100644 --- a/doc/guide/files/submit.xml +++ b/doc/guide/files/submit.xml @@ -1,4 +1,4 @@ - + Submitting and Committing @@ -15,13 +15,14 @@ see . + Submitting source packages (for non-NetBSD-developers) First, check that your package is complete, compiles and runs well; see and the rest of this document. Next, generate an uuencoded gzipped &man.tar.1; - archive, preferably with all files in a single directory. + archive that contains all files that make up the package. Finally, send-pr with category pkg, a synopsis which includes the package name and version number, a short description of your package @@ -38,6 +39,7 @@ for details. + General notes when adding, updating, or removing packages diff --git a/doc/guide/files/using.xml b/doc/guide/files/using.xml index c7ae22f5427..87707b65421 100644 --- a/doc/guide/files/using.xml +++ b/doc/guide/files/using.xml @@ -1,4 +1,4 @@ - + Using pkgsrc @@ -30,7 +30,7 @@ - These prebuilt package tools use + These pre-built package tools use /usr/pkg for the base directory, and /var/db/pkg for the database of installed packages. If you cannot use these directories for whatever @@ -85,7 +85,7 @@ automatically by giving pkg_add an FTP URL: - # pkg_add ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/All/package.tgz + # pkg_add ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/All/package Note that any prerequisite packages needed to run the package in question will be installed, too, assuming they are @@ -116,6 +116,49 @@ installed program. + +Deinstalling packages + + To deinstall a package, it does not matter whether it was + installed from source code or from a binary package. The + pkg_delete command does not know it anyway. + To delete a package, you can just run pkg_delete + package-name. The package + name can be given with or without version number. Wildcards can + also be used to deinstall a set of packages, for example + *emacs*. Be sure to include them in quotes, + so that the shell does not expand them before + pkg_delete sees them. + + The option is very powerful: it + removes all the packages that require the package in question + and then removes the package itself. For example: + + + &rprompt; pkg_delete -r jpeg + + + will remove jpeg and all the packages that used it; this allows + upgrading the jpeg package. + + + + +Getting information about installed packages + + The pkg_info shows information about + installed packages or binary package files. + + + + +Other administrative functions + + The pkg_admin executes various + administrative functions on the package system. + + + A word of warning @@ -145,11 +188,12 @@ Requirements - To build packages from source on a NetBSD system the - comp and the text distribution - sets must be installed. If you want to build X11-related - packages the xbase and xcomp - distribution sets are required, too. + To build packages from source, you need a working C + compiler. On NetBSD, you need to install the + comp and the text distribution + sets. If you want to build X11-related packages, the + xbase and xcomp distribution + sets are required, too. -- cgit v1.2.3