90f0ef4799
into a separate package pkgtools/bootstrap-extras. Teach the bootstrap script to look for those scripts from the bootstrap-extras package. * When registering the installed software, set WRKOBJDIR to the bootstrap work directory to protect against a read-only pkgsrc tree. |
||
---|---|---|
.. | ||
bootstrap | ||
cleanup | ||
mkbinarykit | ||
mkbootstrapkit | ||
README | ||
README.AIX | ||
README.Darwin | ||
README.FreeBSD | ||
README.Interix | ||
README.IRIX | ||
README.IRIX5.3 | ||
README.Linux | ||
README.MacOSX | ||
README.OpenBSD | ||
README.OSF1 | ||
README.Solaris | ||
testbootstrap | ||
ufsdiskimage |
$NetBSD: README,v 1.7 2005/11/08 17:25:30 reed Exp $ To try to get pkgsrc working on your system, please try the following as root: # ./bootstrap [ --workdir <workdir> ] [ --prefix <prefix> ] [ --pkgdbdir <pkgdbdir> ] [ --sysconfdir <sysconfdir> ] [ --varbase <varbase> ] [ --ignore-case-check ] [ --ignore-user-check ] [ --preserve-path ] [ --help ] The defaults for the arguments are as follows: --prefix /usr/pkg --pkgdbdir /var/db/pkg --sysconfdir /usr/pkg/etc --varbase /var --workdir work It is perfectly acceptable to place 'pkgdbdir' under 'prefix'. The working directory will be created if it doesn't exist and has to be writable by the user executing ./bootstrap. Make sure that you have a working C compiler and make(1) binary in your path. Please note that on some systems (IRIX and SunOS, for example), the bootstrap script will look into a number of common directories for alternative implementations of some tools. If they are found, these directories will be prepended to the PATH variable, unless the '--preserve-path' flag is given. See pkgsrc/doc/pkgsrc.txt or http://www.netbsd.org/Documentation/software/packages.html for more information about bootstrapping and using pkgsrc. We'd be very interested in hearing of any successes or failures on "unknown" (to us) systems. Please remember to add $prefix/bin to your PATH environment variable and $prefix/man to your MANPATH environment variable, if necessary. (See above for --prefix and its default value.) The bootstrap script will create an example mk.conf file located in your work directory as "mk.conf.example". It conatins the settings you provided to the bootstrap. Copy it to your $sysconfdir directory (see above about --sysconfdir and its default value).