Pkgsrc in PC-BSD® - Revision history

Tigersharke: /* Setting things up */

2012-10-12T10:35:16Z

‎Setting things up

Tigersharke: /* Setting things up */ minor inaccuracy - text didn't match command it described.

2012-10-12T10:33:42Z

‎Setting things up: minor inaccuracy - text didn't match command it described.

Tigersharke at 10:30, 12 October 2012

2012-10-12T10:30:19Z

Tigersharke: /* Keeping pkgsrc up to date */

2012-10-12T09:56:40Z

‎Keeping pkgsrc up to date

Tigersharke: I don't think I originally intended that line numbered as 4 was to be numbered, but this seems only way to have similar formatting indents.

2012-10-12T09:53:37Z

I don't think I originally intended that line numbered as 4 was to be numbered, but this seems only way to have similar formatting indents.

Vater: form (please check)

2012-10-11T14:33:30Z

form (please check)

Tigersharke at 07:44, 11 October 2012

2012-10-11T07:44:17Z

Tigersharke at 07:39, 11 October 2012

2012-10-11T07:39:52Z

Vater at 17:33, 10 October 2012

2012-10-10T17:33:36Z

Drulavigne at 13:52, 23 August 2012

2012-08-23T13:52:51Z

@@ Line 23: / Line 23: @@
 #: {{pound}} /usr/pkg/sbin/pkg_admin -K fetch-pkg-vulnerabilities<br>
 #: This prevents the non-fatal error below:<br>
-#:: WARNING: No /var/db/pkg/pkg-vulnerabilities file found.<br<
+#:: WARNING: No /var/db/pkg/pkg-vulnerabilities file found.<br>
 #:: WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'.<br>
 # The vulnerabilities of some ports (ie Firefox) may prevent them from being built. An example mk.conf file will be placed in /etc/mk.conf.example file when you use the bootstrap script. Adjust /usr/pkg/etc/mk.conf to allow vulnerable programs to be built by adding the following line:

@@ Line 8: / Line 8: @@
 #: {{pound}} ftp {{ftp}}ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz<br>
 #: {{pound}} tar -xzf pkgsrc.tar.gz -C /usr<br>
-# Bootstrap pkgsrc. FreeBSD stores its ports pkg database in /var/db/pkg/. It is therefore recommended to use /usr/db/pkgsrc/ with the --pkgdbdir flag as below:<br>
+# Bootstrap pkgsrc. FreeBSD stores its ports pkg database in /var/db/pkg/. It is therefore recommended to use /var/db/pkgsrc/ with the --pkgdbdir flag as below:<br>
 #: {{pound}} cd /usr/pkgsrc/bootstrap/<br>{{pound}} ./bootstrap --pkgdbdir /var/db/pkgsrc<br>
 # The NetBSD pkg tools and FreeBSD pkg tools have identical names. It is recommended to change the name of the NetBSD set to match 'bmake' by prepending a 'b' to each, as follows:

@@ Line 67: / Line 67: @@
 However, if there may be options that would modify what is built, how it is installed, or the features enabled. The additional steps for options adjustment is done prior to invoking ''bmake install clean.'' Discover whether there are options:
-: {{pound}} bmake show-options
+{{cli|xterm=
- <nowiki>
+Any of the following general options may be selected:<br>
-Any of the following general options may be selected:
+:	official-mozilla-branding&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;	Use official Mozilla reg. trademarks and logos.
-	official-mozilla-branding	Use official Mozilla reg. trademarks and logos.
 These options are enabled by default:
@@ Line 79: / Line 79: @@
 You can select which build options to use by setting PKG_DEFAULT_OPTIONS
 or PKG_OPTIONS.firefox.
- </nowiki>
+}}
 == Adding a NetBSD pkg ==
@@ Line 85: / Line 85: @@
 : {{pound}} bpkg_add firefox
-The above probably should simply work, or the NetBSD documentation would not mention renaming the FreeBSD pkg tools. However, for the moment, testing throws the following type of error:
+The above probably should simply work, or the NetBSD documentation would not mention renaming the FreeBSD pkg tools. However, for the moment, testing this throws the following type of error:
- <nowiki>
+{{cli|xterm=
-pkg_add: Warning: package `firefox-3.6.16' was built for a platform:
+pkg_add: Warning: package `firefox-3.6.16' was built for a platform:<br>
-pkg_add: NetBSD/x86_64 5.1 (pkg) vs. FreeBSD/x86_64 9.0 (this host)
+pkg_add: NetBSD/x86_64 5.1 (pkg) vs. FreeBSD/x86_64 9.0 (this host)<br>
-pkg_add: 1 package addition failed
+pkg_add: 1 package addition failed<br>
- </nowiki>
+}}

@@ Line 31: / Line 31: @@
 # The process for using tar files is very much the same as when obtaining them originally, except that the old tree must be erased first<br>
-#: {{pound}} rm -rf /usr/pkgsrc/<br><nowiki># ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</nowiki><br>
+#: {{pound}} rm -rf /usr/pkgsrc/<br>
 #: {{pound}} tar -xzf pkgsrc.tar.gz -C /usr<br>
 # Next bootstrap pkgsrc again<br>
 #: {{pound}} cd /usr/pkgsrc/bootstrap/<br>
 #: {{pound}} ./bootstrap --pkgdbdir /var/db/pkgsrc<br>
-# Update the bootstrap-mk-files<br><br>{{pound}} cd /usr/pkgsrc/pkgtools/bootstrap-mk-files/<br>{{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake update<br><br>And if that does not work (such as on a standard NetBSD install) try:<br>
+# Update the bootstrap-mk-files<br>
-#: {{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake replace<br>{{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake update<br>
+#: {{pound}} cd /usr/pkgsrc/pkgtools/bootstrap-mk-files/
   <nowiki>

@@ Line 10: / Line 10: @@
 # Bootstrap pkgsrc. FreeBSD stores its ports pkg database in /var/db/pkg/. It is therefore recommended to use /usr/db/pkgsrc/ with the --pkgdbdir flag as below:<br>
 #: {{pound}} cd /usr/pkgsrc/bootstrap/<br>{{pound}} ./bootstrap --pkgdbdir /var/db/pkgsrc<br>
-# The NetBSD pkg tools and FreeBSD pkg tools have identical names. It is recommended to change the name of the NetBSD set to match 'bmake' by prepending a 'b' to each, as follows:<br>
+# The NetBSD pkg tools and FreeBSD pkg tools have identical names. It is recommended to change the name of the NetBSD set to match 'bmake' by prepending a 'b' to each, as follows:
-#: {{pound}} cd /usr/pkg/sbin/<br>{{pound}} mv pkg_add bpkg_add<br>{{pound}} mv pkg_create bpkg_create<br>
+#: {{pound}} cd /usr/pkg/sbin/<br>{{pound}} mv pkg_add bpkg_add<br>{{pound}} mv pkg_create bpkg_create
-#: {{pound}} mv pkg_delete bpkg_delete<br>{{pound}} mv pkg_info bpkg_info<br>
+#: {{pound}} mv pkg_delete bpkg_delete<br>{{pound}} mv pkg_info bpkg_info
-#: If the FreeBSD ports tools will not be used, they can be moved out of the way as follows:<br>
+# If the FreeBSD ports tools will not be used, they can be moved out of the way entirely, as follows:
-#:: {{pound}} cd /usr/sbin/<br>{{pound}} mv pkg_add pkg_add.orig<br>
+#: {{pound}} cd /usr/sbin/<br>{{pound}} mv pkg_add pkg_add.orig<br>
-#:: {{pound}} mv pkg_create pkg_create.orig<br>{{pound}} mv pkg_delete pkg_delete.orig<br>{{pound}} mv pkg_info pkg_info.orig<br>
+#: {{pound}} mv pkg_create pkg_create.orig<br>{{pound}} mv pkg_delete pkg_delete.orig<br>{{pound}} mv pkg_info pkg_info.orig<br>
 # Add the location of bmake (/usr/pkg/bin) and NetBSD pkg tools (/usr/pkg/sbin) to the user's search path variable. Edit the file .cshrc in the user's home directory to modify the following line:
 #: set path = (/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin /usr/local/bin '''/usr/pkg/sbin /usr/pkg/bin''' $HOME/bin)<br>

@@ Line 1: / Line 1: @@
 {{NavHome}}
-==Keeping pkgsrc up to date==
+Available to PC-BSD® is its own PBI collection, FreeBSD ports, and FreeBSD packages. However, it is also possible to use the NetBSD pkgsrc system to build software.  This is not (yet) a pre-configured feature, which means there are some special instructions to follow for this functionality to be enabled. '''This is not an official feature.''' This section will describe how to configure and use NetBSD pkgsrc from PC-BSD®.<br>'''NOTE:''' Although these instructions seem complete and look polished, there may still be ommissions or inaccuracies, so be wary.
-# The process for using tar files is very much the same as when obtaining them originally, except that the old tree must be erased first<br><br>{{pound}} rm -rf /usr/pkgsrc/<br><nowiki># ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</nowiki><br>{{pound}} tar -xzf pkgsrc.tar.gz -C /usr<br><br>
-# Next bootstrap pkgsrc again<br><br>{{pound}} cd /usr/pkgsrc/bootstrap/<br>{{pound}} ./bootstrap --pkgdbdir /var/db/pkgsrc<br><br>
+== Setting things up ==
-# Update the bootstrap-mk-files<br><br>{{pound}} cd /usr/pkgsrc/pkgtools/bootstrap-mk-files/<br>{{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake update<br><br>And if that does not work (such as on a standard NetBSD install) try:<br><br>{{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake replace<br>{{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake update<br>
   <nowiki>
@@ Line 24: / Line 48: @@
 ERROR:
 ERROR:     - "/usr/pkgsrc/bootstrap/work/bin/bmake replace" to replace only the package without re-linking dependencies,
-ERROR:      risking various problems. </nowiki>
+ERROR:      risking various problems.
 Much like using the FreeBSD ports system, building with the NetBSD pkgsrc system is a rather simple matter of going to the location of the application within the pkgsrc tree, and then using bmake, for example:
-:{{percent}} su -m
+: {{percent}} su -m
-:{{pound}} unsetenv PKG_PATH
+: {{pound}} unsetenv PKG_PATH
-:{{pound}} cd /usr/pkgsrc/www/firefox/
+: {{pound}} cd /usr/pkgsrc/www/firefox/
-:{{pound}} bmake install clean
+: {{pound}} bmake install clean
 However, if there may be options that would modify what is built, how it is installed, or the features enabled. The additional steps for options adjustment is done prior to invoking ''bmake install clean.'' Discover whether there are options:
-:{{pound}} bmake show-options
+: {{pound}} bmake show-options
   <nowiki>
 Any of the following general options may be selected:
@@ Line 47: / Line 74: @@
 You can select which build options to use by setting PKG_DEFAULT_OPTIONS
 or PKG_OPTIONS.firefox.
-</nowiki>
+ </nowiki>
-==Adding a NetBSD pkg==
+== Adding a NetBSD pkg ==
-:{{percent}} su -m
+: {{percent}} su -m
-:{{pound}} bpkg_add firefox
+: {{pound}} bpkg_add firefox
 The above probably should simply work, or the NetBSD documentation would not mention renaming the FreeBSD pkg tools. However, for the moment, testing throws the following type of error:
@@ Line 58: / Line 85: @@
 pkg_add: Warning: package `firefox-3.6.16' was built for a platform:
 pkg_add: NetBSD/x86_64 5.1 (pkg) vs. FreeBSD/x86_64 9.0 (this host)
-pkg_add: 1 package addition failed</nowiki>
+pkg_add: 1 package addition failed

@@ Line 2: / Line 2: @@
 Available to PC-BSD® is its own PBI collection, FreeBSD ports, and FreeBSD packages. However, it is also possible to use the NetBSD pkgsrc system to build software.  This is not (yet) a pre-configured feature, which means there are some special instructions to follow for this functionality to be enabled. '''This is not an official feature.''' This section will describe how to configure and use NetBSD pkgsrc from PC-BSD®. <br>'''NOTE:''' Although these instructions seem complete and look polished, there may still be ommissions or inaccuracies, so be wary.
 ==Setting things up==
-# Obtain the NetBSD pkgsrc tree by the following commands:<br><br><nowiki># ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</nowiki><br>{{pound}} tar -xzf pkgsrc.tar.gz -C /usr<br><br>
+# Obtain the NetBSD pkgsrc tree by the following commands:<br><br>{{pound}} ftp {{ftp}}ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz<br>{{pound}} tar -xzf pkgsrc.tar.gz -C /usr<br><br>
 # Bootstrap pkgsrc. FreeBSD stores its ports pkg database in /var/db/pkg/. It is therefore recommended to use /usr/db/pkgsrc/ with the --pkgdbdir flag as below:<br><br>{{pound}} cd /usr/pkgsrc/bootstrap/<br>{{pound}} ./bootstrap --pkgdbdir /var/db/pkgsrc<br><br>
 # The NetBSD pkg tools and FreeBSD pkg tools have identical names. It is recommended to change the name of the NetBSD set to match 'bmake' by prepending a 'b' to each, as follows:<br><br>{{pound}} cd /usr/pkg/sbin/<br>{{pound}} mv pkg_add bpkg_add<br>{{pound}} mv pkg_create bpkg_create<br>{{pound}} mv pkg_delete bpkg_delete<br>{{pound}} mv pkg_info bpkg_info<br><br>If the FreeBSD ports tools will not be used, they can be moved out of the way as follows:<br><br>{{pound}} cd /usr/sbin/<br>{{pound}} mv pkg_add pkg_add.orig<br>{{pound}} mv pkg_create pkg_create.orig<br>{{pound}} mv pkg_delete pkg_delete.orig<br>{{pound}} mv pkg_info pkg_info.orig<br><br>
@@ Line 29: / Line 29: @@
 Much like using the FreeBSD ports system, building with the NetBSD pkgsrc system is a rather simple matter of going to the location of the application within the pkgsrc tree, and then using bmake, for example:
-:<nowiki>%</nowiki>su -m
+:{{percent}} su -m
 :{{pound}} unsetenv PKG_PATH
 :{{pound}} cd /usr/pkgsrc/www/firefox/
@@ Line 50: / Line 50: @@
 ==Adding a NetBSD pkg==
-:<nowiki>%</nowiki>su -m
+:{{percent}} su -m
 :{{pound}} bpkg_add firefox

@@ Line 13: / Line 13: @@
 # The process for using tar files is very much the same as when obtaining them originally, except that the old tree must be erased first<br><br><nowiki>#</nowiki> rm -rf /usr/pkgsrc/<br><nowiki># ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</nowiki><br><nowiki>#</nowiki> tar -xzf pkgsrc.tar.gz -C /usr<br><br>
 # Next bootstrap pkgsrc again<br><br><nowiki>#</nowiki> cd /usr/pkgsrc/bootstrap/<br><nowiki>#</nowiki> ./bootstrap --pkgdbdir /var/db/pkgsrc<br><br>
-# Update the bootstrap-mk-files<br><br><nowiki>#</nowiki> cd /usr/pkgsrc/pkgtools/bootstrap-mk-files/<br><nowiki>#</nowiki> /usr/pkgsrc/bootstrap/work/bin/bmake update<br><br>And if that doesn't work (such as on a standard NetBSD install) try:<br><br><nowiki>#</nowiki> /usr/pkgsrc/bootstrap/work/bin/bmake replace<br><nowiki>#</nowiki> /usr/pkgsrc/bootstrap/work/bin/bmake update<br>
+# Update the bootstrap-mk-files<br><br><nowiki>#</nowiki> cd /usr/pkgsrc/pkgtools/bootstrap-mk-files/<br><nowiki>#</nowiki> /usr/pkgsrc/bootstrap/work/bin/bmake update<br><br>And if that does not work (such as on a standard NetBSD install) try:<br><br><nowiki>#</nowiki> /usr/pkgsrc/bootstrap/work/bin/bmake replace<br><nowiki>#</nowiki> /usr/pkgsrc/bootstrap/work/bin/bmake update<br>
   <nowiki>