head 1.22; access; symbols pkgsrc-2019Q4:1.21.0.10 pkgsrc-2019Q4-base:1.21 pkgsrc-2019Q3:1.21.0.6 pkgsrc-2019Q3-base:1.21 pkgsrc-2019Q2:1.21.0.4 pkgsrc-2019Q2-base:1.21 pkgsrc-2019Q1:1.21.0.2 pkgsrc-2019Q1-base:1.21 pkgsrc-2018Q4:1.20.0.2 pkgsrc-2018Q4-base:1.20 pkgsrc-2018Q3:1.19.0.16 pkgsrc-2018Q3-base:1.19 pkgsrc-2018Q2:1.19.0.14 pkgsrc-2018Q2-base:1.19 pkgsrc-2018Q1:1.19.0.12 pkgsrc-2018Q1-base:1.19 pkgsrc-2017Q4:1.19.0.10 pkgsrc-2017Q4-base:1.19 pkgsrc-2017Q3:1.19.0.8 pkgsrc-2017Q3-base:1.19 pkgsrc-2017Q2:1.19.0.4 pkgsrc-2017Q2-base:1.19 pkgsrc-2017Q1:1.19.0.2 pkgsrc-2017Q1-base:1.19 pkgsrc-2016Q4:1.18.0.98 pkgsrc-2016Q4-base:1.18 pkgsrc-2016Q3:1.18.0.96 pkgsrc-2016Q3-base:1.18 pkgsrc-2016Q2:1.18.0.94 pkgsrc-2016Q2-base:1.18 pkgsrc-2016Q1:1.18.0.92 pkgsrc-2016Q1-base:1.18 pkgsrc-2015Q4:1.18.0.90 pkgsrc-2015Q4-base:1.18 pkgsrc-2015Q3:1.18.0.88 pkgsrc-2015Q3-base:1.18 pkgsrc-2015Q2:1.18.0.86 pkgsrc-2015Q2-base:1.18 pkgsrc-2015Q1:1.18.0.84 pkgsrc-2015Q1-base:1.18 pkgsrc-2014Q4:1.18.0.82 pkgsrc-2014Q4-base:1.18 pkgsrc-2014Q3:1.18.0.80 pkgsrc-2014Q3-base:1.18 pkgsrc-2014Q2:1.18.0.78 pkgsrc-2014Q2-base:1.18 pkgsrc-2014Q1:1.18.0.76 pkgsrc-2014Q1-base:1.18 pkgsrc-2013Q4:1.18.0.74 pkgsrc-2013Q4-base:1.18 pkgsrc-2013Q3:1.18.0.72 pkgsrc-2013Q3-base:1.18 pkgsrc-2013Q2:1.18.0.70 pkgsrc-2013Q2-base:1.18 pkgsrc-2013Q1:1.18.0.68 pkgsrc-2013Q1-base:1.18 pkgsrc-2012Q4:1.18.0.66 pkgsrc-2012Q4-base:1.18 pkgsrc-2012Q3:1.18.0.64 pkgsrc-2012Q3-base:1.18 pkgsrc-2012Q2:1.18.0.62 pkgsrc-2012Q2-base:1.18 pkgsrc-2012Q1:1.18.0.60 pkgsrc-2012Q1-base:1.18 pkgsrc-2011Q4:1.18.0.58 pkgsrc-2011Q4-base:1.18 pkgsrc-2011Q3:1.18.0.56 pkgsrc-2011Q3-base:1.18 pkgsrc-2011Q2:1.18.0.54 pkgsrc-2011Q2-base:1.18 pkgsrc-2011Q1:1.18.0.52 pkgsrc-2011Q1-base:1.18 pkgsrc-2010Q4:1.18.0.50 pkgsrc-2010Q4-base:1.18 pkgsrc-2010Q3:1.18.0.48 pkgsrc-2010Q3-base:1.18 pkgsrc-2010Q2:1.18.0.46 pkgsrc-2010Q2-base:1.18 pkgsrc-2010Q1:1.18.0.44 pkgsrc-2010Q1-base:1.18 pkgsrc-2009Q4:1.18.0.42 pkgsrc-2009Q4-base:1.18 pkgsrc-2009Q3:1.18.0.40 pkgsrc-2009Q3-base:1.18 pkgsrc-2009Q2:1.18.0.38 pkgsrc-2009Q2-base:1.18 pkgsrc-2009Q1:1.18.0.36 pkgsrc-2009Q1-base:1.18 pkgsrc-2008Q4:1.18.0.34 pkgsrc-2008Q4-base:1.18 pkgsrc-2008Q3:1.18.0.32 pkgsrc-2008Q3-base:1.18 cube-native-xorg:1.18.0.30 cube-native-xorg-base:1.18 pkgsrc-2008Q2:1.18.0.28 pkgsrc-2008Q2-base:1.18 cwrapper:1.18.0.26 pkgsrc-2008Q1:1.18.0.24 pkgsrc-2008Q1-base:1.18 pkgsrc-2007Q4:1.18.0.22 pkgsrc-2007Q4-base:1.18 pkgsrc-2007Q3:1.18.0.20 pkgsrc-2007Q3-base:1.18 pkgsrc-2007Q2:1.18.0.18 pkgsrc-2007Q2-base:1.18 pkgsrc-2007Q1:1.18.0.16 pkgsrc-2007Q1-base:1.18 pkgsrc-2006Q4:1.18.0.14 pkgsrc-2006Q4-base:1.18 pkgsrc-2006Q3:1.18.0.12 pkgsrc-2006Q3-base:1.18 pkgsrc-2006Q2:1.18.0.10 pkgsrc-2006Q2-base:1.18 pkgsrc-2006Q1:1.18.0.8 pkgsrc-2006Q1-base:1.18 pkgsrc-2005Q4:1.18.0.6 pkgsrc-2005Q4-base:1.18 pkgsrc-2005Q3:1.18.0.4 pkgsrc-2005Q3-base:1.18 pkgsrc-2005Q2:1.18.0.2 pkgsrc-2005Q2-base:1.18 pkgsrc-2005Q1:1.17.0.10 pkgsrc-2005Q1-base:1.17 pkgsrc-2004Q4:1.17.0.8 pkgsrc-2004Q4-base:1.17 pkgsrc-2004Q3:1.17.0.6 pkgsrc-2004Q3-base:1.17 pkgsrc-2004Q2:1.17.0.4 pkgsrc-2004Q2-base:1.17 pkgsrc-2004Q1:1.17.0.2 pkgsrc-2004Q1-base:1.17 pkgsrc-2003Q4:1.16.0.2 pkgsrc-2003Q4-base:1.16 netbsd-1-6-1:1.13.0.6 netbsd-1-6-1-base:1.13 netbsd-1-6:1.13.0.8 netbsd-1-6-RELEASE-base:1.13 pkgviews:1.13.0.4 pkgviews-base:1.13 buildlink2:1.13.0.2 buildlink2-base:1.13 netbsd-1-5-PATCH003:1.13 netbsd-1-5-PATCH001:1.11 netbsd-1-5-RELEASE:1.11 netbsd-1-4-PATCH003:1.11 netbsd-1-4-PATCH002:1.9 comdex-fall-1999:1.8 netbsd-1-4-PATCH001:1.8 netbsd-1-4-RELEASE:1.8 netbsd-1-3-PATCH003:1.8 netbsd-1-3-PATCH002:1.5; locks; strict; comment @# @; 1.22 date 2020.01.13.21.05.50; author nia; state dead; branches; next 1.21; commitid oocjsbsX3eiZBzSB; 1.21 date 2019.01.29.03.11.03; author gutteridge; state Exp; branches; next 1.20; commitid jNUAkKHebjPJSC9B; 1.20 date 2018.10.09.22.55.48; author maya; state Exp; branches; next 1.19; commitid ZqL7qsMzFh4k2lVA; 1.19 date 2017.03.02.09.51.35; author maya; state Exp; branches; next 1.18; commitid of3w62Z0kosUvXHz; 1.18 date 2005.05.07.22.18.28; author wiz; state Exp; branches; next 1.17; 1.17 date 2004.03.13.11.31.43; author grant; state Exp; branches; next 1.16; 1.16 date 2003.06.23.07.48.01; author grant; state Exp; branches; next 1.15; 1.15 date 2003.05.06.17.40.18; author jmmv; state Exp; branches; next 1.14; 1.14 date 2003.05.05.14.23.09; author cjep; state Exp; branches; next 1.13; 1.13 date 2001.12.03.21.33.56; author agc; state Exp; branches; next 1.12; 1.12 date 2001.06.06.19.41.05; author hubertf; state Exp; branches; next 1.11; 1.11 date 2000.07.23.18.02.33; author fredb; state Exp; branches; next 1.10; 1.10 date 2000.07.23.17.59.17; author fredb; state Exp; branches; next 1.9; 1.9 date 2000.01.14.10.32.35; author abs; state Exp; branches; next 1.8; 1.8 date 98.09.01.11.03.23; author agc; state Exp; branches; next 1.7; 1.7 date 98.08.21.19.11.10; author perry; state Exp; branches; next 1.6; 1.6 date 98.07.13.15.42.41; author hubertf; state Exp; branches; next 1.5; 1.5 date 98.04.30.20.58.13; author frueauf; state Exp; branches; next 1.4; 1.4 date 98.04.25.10.51.02; author frueauf; state Exp; branches; next 1.3; 1.3 date 98.04.24.13.55.58; author agc; state Exp; branches; next 1.2; 1.2 date 98.01.13.13.13.59; author agc; state Exp; branches; next 1.1; 1.1 date 98.01.06.19.51.52; author hubertf; state Exp; branches; next ; desc @@ 1.22 log @Markdownify README. @ text @$NetBSD: README,v 1.21 2019/01/29 03:11:03 gutteridge Exp $ pkgsrc is a framework for building software on UNIX-like systems. To use, bootstrap using: cd pkgsrc/bootstrap/ ./bootstrap build packages, use: cd pkgsrc/category/package-name $PREFIX/bin/bmake install Where $PREFIX is where you've chosen to install packages (typically /usr/pkg) Bugs and patches can be filed in the following link (use category 'pkg'): https://www.netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd To fetch the main CVS repository: cvs -d anoncvs@@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc It's also possible to contribute through pkgsrc wip (work in progress), for more information, see http://pkgsrc.org/wip/users/ Please see doc/pkgsrc.txt for information. @ 1.21 log @README: minor grammatical fix @ text @d1 1 a1 1 $NetBSD: README,v 1.20 2018/10/09 22:55:48 maya Exp $ @ 1.20 log @Don't prefix commands by a shell prompt, so they're slightly easier to copy. @ text @d1 1 a1 1 $NetBSD: README,v 1.19 2017/03/02 09:51:35 maya Exp $ d15 1 a15 1 Bugs and patches can be filed in the follow link (use category 'pkg'): @ 1.19 log @Make top dir README a little more helpful. This file is very prominent on github, so use this opportunity to give a quick intro to pkgsrc. mention main repo location so it's obvious even when using a fork & bug report address. @ text @d1 1 a1 1 $NetBSD: README,v 1.18 2005/05/07 22:18:28 wiz Exp $ d6 2 a7 2 % cd pkgsrc/bootstrap/ % ./bootstrap d10 2 a11 2 % cd pkgsrc/category/package-name % $PREFIX/bin/bmake install d19 1 a19 1 % cvs -d anoncvs@@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc @ 1.18 log @Refer doc/pkgsrc.txt instead of Packages.txt. @ text @d1 22 a22 1 $NetBSD: README,v 1.17 2004/03/13 11:31:43 grant Exp $ @ 1.17 log @the pkgsrc documentation is in Packages.txt right now, as the XML documentation isn't ready yet. @ text @d1 1 a1 1 $NetBSD: README,v 1.16 2003/06/23 07:48:01 grant Exp $ d3 1 a3 2 Please see Packages.txt in the top level pkgsrc directory (this directory) for information. @ 1.16 log @the full documentation has more up-to-date information than the README, deprecate it, too. @ text @d1 1 a1 1 $NetBSD$ d3 2 a4 13 The pkgsrc documentation now lives on the NetBSD web site. Full documentation, one file per chapter: http://www.NetBSD.org/Documentation/pkgsrc/ Full documentation in a single file: http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.html Full documentation in a single plain-text file: http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.txt pkgsrc.txt and pkgsrc.html are also provided in the top level pkgsrc directory (this directory). @ 1.15 log @Drop trailing whitespace. Ok'ed by wiz. @ text @d1 1 a1 1 $NetBSD: README,v 1.14 2003/05/05 14:23:09 cjep Exp $ d3 1 a3 2 Welcome to the NetBSD Packages Collection ========================================= d5 2 a6 2 In brief, the NetBSD Packages Collection is a set of software utilities and libraries which have been ported to NetBSD. d8 2 a9 6 The packages collection software can retrieve the software from its home site, assuming you are connected in some way to the Internet, verify its integrity, apply any patches, configure the software for NetBSD, and build it. Any prerequisite software will also be built and installed for you. Installation and de-installation of software is managed by the packaging utilities. d11 2 a12 1 The packages collection is made into a tar_file every week: d14 2 a15 75 ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz and you can sup the pkgsrc tree using the `pkgsrc' name for the collection. The pkgsrc tree is laid out in various categories, and, within that, the various packages themselves. You need to have root privileges to install packages. We are looking at ways to remove this restriction. + To install a package on your system, you need to change into the directory of the package, and type "make install". + If you've made a mistake, and decided that you don't want that package on your system, then type "pkg_delete ", or "make deinstall" while in the directory for the package. + To find out all the packages that you have installed on your system, type "pkg_info". + To remove the work directory, type "make clean", and "make clean-depends" will clean up any working directories for other packages that are built in the process of making your package. + Optionally, you can periodically run "make clean" from the top level pkgsrc directory. This will delete extracted and built files, but will not affect the retreived source sets in pkgsrc/distfiles. + You can set variables to customise the behaviour (where packages are installed, various options for individual packages etc), by setting variables in /etc/mk.conf. The pkgsrc/mk/bsd.pkg.defaults.mk gives the defaults which are used in pkgsrc. This file can be used as a guide to set values in /etc/mk.conf - it is only necessary to set values where they differ from the defaults. The best way to find out what packages are in the collection is to move to the top-level pkgsrc directory (this will usually be /usr/pkgsrc), and type "make readme". This will create a file called README.html in the top-level pkgsrc directory, and also in all category and package directories. You can then see what packages are available, along with a short (one-line) comment about the function of the package, and a pointer to a fuller description, by using a browser like lynx (see pkgsrc/www/lynx) or Mozilla (pkgsrc/www/mozilla), or Communicator. This is also available online as ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/README.html. Another way to find out what packages are in the collection is to move to the top-level pkgsrc directory and type "make index". This will create pkgsrc/INDEX which can be viewed via "make print-index | more". You can also search for particular packages or keywords via "make search key=". It is also possible to use the packaging software to install pre-compiled binary packages by typing "pkg_add ". To see what binary packages are available, see: ftp://ftp.netbsd.org/pub/NetBSD/packages///All/ where is the NetBSD release, and is the hardware architecture. One limitation of using binary packages provided from ftp.netbsd.org is that all mk.conf options were set to the defaults at compile time. LOCALBASE, in particular, defaults to /usr/pkg, so non-X binaries will be installed in /usr/pkg/bin, man pages will be installed in /usr/pkg/man... When a packaged tool has major compile time choices, such as support for multiple graphic toolkit libraries, the different options may be available as separate packages. For more information on the packages collection see the file Packages.txt file in the same place where you found this README, usually in the top-level pkgsrc directory. @ 1.14 log @dir -> directory @ text @d1 1 a1 1 $NetBSD: README,v 1.13 2001/12/03 21:33:56 agc Exp $ d16 1 a16 1 The packages collection is made into a tar_file every week: d72 1 a72 1 pre-compiled binary packages by typing "pkg_add ". @ 1.13 log @Update a sentence which used to talk about mk.conf.example to explain the use of bsd.pkg.defaults.mk. Pointed out by jhawk. @ text @d1 1 a1 1 $NetBSD: README,v 1.12 2001/06/06 19:41:05 hubertf Exp $ d92 1 a92 2 usually in the top-level pkgsrc dir. directory. @ 1.12 log @update a bit @ text @d1 1 a1 1 $NetBSD: README,v 1.11 2000/07/23 18:02:33 fredb Exp $ d49 4 a52 2 variables in /etc/mk.conf. The pkgsrc/mk/mk.conf.example file provides some examples for customisation. @ 1.11 log @No paragraph (picking nits). @ text @d1 1 a1 1 $NetBSD: README,v 1.10 2000/07/23 17:59:17 fredb Exp $ d89 2 a90 1 Packages.txt where you found this README, or in your top-level pkgsrc @ 1.10 log @"is the default" -> "defaults to". Separate parallel clauses with a comma. @ text @d1 1 a1 1 $NetBSD: README,v 1.9 2000/01/14 10:32:35 abs Exp $ a79 1 @ 1.9 log @some corrections by David Maxwell @ text @d1 1 a1 1 $NetBSD: README,v 1.8 1998/09/01 11:03:23 agc Exp $ d81 2 a82 2 LOCALBASE, in particular, is the default /usr/pkg, so non-X binaries will be installed in /usr/pkg/bin. Man pages will be installed in @ 1.8 log @Minor mods to clean up the English. @ text @d1 1 a1 1 $NetBSD: README,v 1.7 1998/08/21 19:11:10 perry Exp $ d30 1 a30 1 directory of the package, and type "make && make install". d34 1 a34 1 deinstall". d43 4 d65 1 a65 1 will create pksrc/INDEX which can be viewed via "make print-index | more". d78 11 d90 2 a91 1 Packages.txt in this directory. @ 1.7 log @note move of Packages.txt @ text @d1 1 a1 1 $NetBSD: README,v 1.6 1998/07/13 15:42:41 hubertf Exp $ d16 1 a16 1 The packages collection is made weekly into a tar_file: d43 4 a46 3 + To find out what variables exists to customize some behaviour of pkgsrc (e.g. where it installs to) have a look at pkgsrc/mk/mk.conf.example. You can set those in /etc/mk.conf. d55 3 a57 3 like lynx (see pkgsrc/www/lynx) or something like Mozilla (pkgsrc/www/mozilla), or Communicator. This is also available online as ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/README.html. d61 1 a61 1 will create pksrc/INDEX which can be watched via "make print-index | more". @ 1.6 log @Minor reformatting, plus mention URL for online pkg list. @ text @d1 1 a1 1 $NetBSD: README,v 1.5 1998/04/30 20:58:13 frueauf Exp $ d73 2 a74 3 For more information on the packages collection see: http://www.netbsd.org/Documentation/netbsd/Packages.txt @ 1.5 log @Note existence of pkgsrc/mk/mk.conf.example for customization. @ text @d1 1 a1 1 $NetBSD: README,v 1.4 1998/04/25 10:51:02 frueauf Exp $ d55 2 a56 1 (pkgsrc/www/mozilla), or Communicator. d73 1 a73 1 See: a75 2 for more information on the packages collection. @ 1.4 log @Add note about another way to get an overview of pkgs in the tree. @ text @d1 1 a1 1 $NetBSD: README,v 1.3 1998/04/24 13:55:58 agc Exp $ d42 4 @ 1.3 log @Re-write this file completely, with the aim of being a simple introduction to the packages collection. @ text @d1 1 a1 1 $NetBSD: README,v 1.2 1998/01/13 13:13:59 agc Exp $ d52 6 @ 1.2 log @Add NetBSD RCS Id, and correct a minor typo. @ text @d1 1 a1 1 $NetBSD$ d3 2 a4 2 Welcome to the NetBSD Packages System ===================================== d6 2 a7 2 Below this directory, you will find packages to build (compiled) programs from sources. To do so, cd into one of the sub-directories, and enter: d9 6 a14 2 make make install d16 1 a16 2 To make a precompiled binary package that can be installed on another system, enter d18 1 a18 1 make package d20 2 a21 5 after that. The precompiled package will be placed in the "packages" subdirectory. A collection of precompiled binary packages can be found on ftp.netbsd.org in /pub/NetBSD/packages. To install a precompiled binary package, hand its filename or an ftp://-URL pointing to it to pkg_add(1). d23 44 a66 2 See http://www.netbsd.org/Documentation/netbsd/Packages.txt for more information on the packages system. @ 1.1 log @Some descriptive text. @ text @d1 2 d20 1 a20 1 binary package, hand it's filename or an ftp://-URL pointing to it to @