Radish alpha
H
HardenedBSD-pkg
rad:z3QDZAW2FAfuLvihrhiyDC9fAD8G9
HardenedBSD Package Manager
Radicle
Git
Commits › 50b2cdd
Update docco on how to build from source to reflect the new autotools reality.
Matthew Seaman committed 12 years ago
commit 50b2cddc4e25ef301683daa9e7f455c9f0f04723
parent 7fdc14b
1 file changed +23 -7
modified README.md
@@ -194,13 +194,17 @@ repositories, updating remote package repositories and installing from them, etc
<a name="installpkgng"></a>

### Installing pkgng
- 
The first thing to start with is to get pkgng installed on your machine.
+ 
In order to build pkgng from source, you will need to have Gnu
+ 
autotools installed.
+ 
	# pkg install autoconf automake libtool
+
+ 
The next thing to do is to get the pkgng sources installed on your machine.

You can grab a development snapshot of pkgng from the [pkgng Github repository][1]



To get the latest version of pkgng from the Git repo, just clone it:
- 
	# git clone https://github.com/freebsd/pkg
+ 
	% git clone https://github.com/freebsd/pkg



Or you can take an already tagged release of pkgng from the above web page as well.
@@ -208,19 +212,31 @@ Just open your browser and download the release you want.


Once you have the pkgng sources, installing it is fairly easy:
- 
	# cd pkgng
- 
	# make && make install && make clean
+ 
	% cd pkgng
+ 
	% ./autogen.sh
+ 
	% ./configure
+ 
	% make
+ 
	# make install
- 
Now you should have pkgng installed on your system.
+ 
Now you should have the latest pkgng installed on your system.
- 
Transferring your packages to pkgng is done by the ports/pkg2ng script (also
- 
installed by the port
+ 
If you're on a 9.x system or earler and did not have a release version
+ 
of pkg(8) installed previously, you will need to run the pkg2ng
+ 
script.  This is only necesaary when converting your system from the
+ 
old pkg_tools style packages.



In order to register your installed packages to pkgng, execute the commands below:



	# cd pkgng/ports

	# sh pkg2ng
+ 
Otherwise, running any pkg(8) command that will attempt to write to
+ 
the local package database will automatically apply any schema
+ 
updates.  Be aware that these may not be backwards compatible --
+ 
although usually you should see no more than a warning message if you
+ 
try and run an older version of pkg(8) against a newer database
+ 
schema.
+ 


<a name="pkghelp"></a>

### Getting help on the commands usage