Up to [cvs.NetBSD.org] / pkgsrc / pkgtools / pkg_comp / files
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Move pkgtools/pkg_comp to pkgtools/pkg_comp1. This is to make room for pkg_comp 2.0, which is coming soon. The new release is significantly different from the 1.x series in features (supports multiple platforms, bootstrap, and pbulk) but also comes with a different configuration syntax.
Pullup ticket #4859 - requested by agc
pkgtools/pkg_comp: bugfix
Revisions pulled up:
- pkgtools/pkg_comp/Makefile 1.55
- pkgtools/pkg_comp/files/pkg_comp.8 1.41
- pkgtools/pkg_comp/files/pkg_comp.sh 1.43
---
Module Name: pkgsrc
Committed By: agc
Date: Sat Nov 21 23:10:27 UTC 2015
Modified Files:
pkgsrc/pkgtools/pkg_comp: Makefile
pkgsrc/pkgtools/pkg_comp/files: pkg_comp.8 pkg_comp.sh
Log Message:
Update pkg_comp to 1.38nb1
pkgsrc uses the "BUILD_TARGET" definition internally as the primary
target for building in a package's WRKDIR. It defaults to "all".
So pkgsrc cd's to ${WRKDIR} and does a "make ${BUILD_TARGET}"
pkg_comp also wants to use the same "BUILD_TARGET" definition
internally for itself to guide the builds for making binary packages.
It's done at a higher level than the pkgsrc definition. It defaults
to "package".
The use of the same name for two different purposes can cause
pkg_comp to fail to build packages. This commit renames the pkg_comp
definition to be "BUILD_PKG_COMP_TARGET".
With this change in place, my pkg_comp builds now complete successfully.
Bump PKGREVISION for the BUILD_PKG_COMP_TARGET fix
Update pkg_comp to 1.38nb1
pkgsrc uses the "BUILD_TARGET" definition internally as the primary
target for building in a package's WRKDIR. It defaults to "all".
So pkgsrc cd's to ${WRKDIR} and does a "make ${BUILD_TARGET}"
pkg_comp also wants to use the same "BUILD_TARGET" definition
internally for itself to guide the builds for making binary packages.
It's done at a higher level than the pkgsrc definition. It defaults
to "package".
The use of the same name for two different purposes can cause
pkg_comp to fail to build packages. This commit renames the pkg_comp
definition to be "BUILD_PKG_COMP_TARGET".
With this change in place, my pkg_comp builds now complete successfully.
Bump PKGREVISION for the BUILD_PKG_COMP_TARGET fix
Remove references to xpkgwedge and USE_XPKGWEDGE flag. Bump version.
Update to pkg_comp 1.37: - Add the GENERATE_PKG_SUMMARY option to tell pkg_comp to generate a pkg_summary.gz file in the packages directory. Useful to later be able to run a packaging tool like pkgin against new binary packages.
Update to 1.36: - Allow specifying packages by their basename, without a category. This affects the arguments to the 'build' command as well as the list of packages provided to AUTO_PACKAGES and BUILD_PACKAGES.
Update to 1.35: * Fix BUILD_PACKAGES to really support multiple packages. Reported by Ian D. Leroux in private mail.
Update to 1.34: - Remove pkg_install version check and rebuild if outdated. pkgsrc is supposed to do that for us. Addresses PR pkg/38323. - Don't bother to explicitly builddigest. pkgsrc DTRT nowadays when PKGSRC_COMPILER includes ccache/distcc.
Update to 1.33: * Make PKG_DBDIR customizable. This sets the variable in mk.conf, in pkg_install.conf and in the environment.
Update to 1.32: * Do not force the install target to take a full package name. pkg_add will automatically pick the latest version. * When building a package as part of makeroot, make sure it actually gets installed. This is to fix a regression with the switch to USE_DESTDIR=yes. Otherwise these packages will get rebuilt later on when needed. * It is common for calls to mktemp to have 6 placeholders in the template, not 4. Make it so.
More closely match man page.
Version 1.31 - make chroot target return its exit status
Update to version 1.30. Approved by MAINTAINER, jmmv@. Add option -N: with the expection of pkgtools/libkver (see manual page about NETBSD_RELEASE) avoid installation of default packages as well as INSTALL_PACKAGES and BUILD_PACKAGES during the creation of the chroot. Note: This is useful for running pbulk in a sandbox created by pkg_comp as binary packages , possibly very low in the build dependencies tree like pkgtools/digest, won't be built by pkg_comp while creating the sandbox hence pbulk won't have to rebuild nearly all packages otherwise already up-to-date. The maintainer notes that this seems like abusing pkg_comp to just create sandboxes. And well... yes indeed!
Update to version 1.29 Ensure that libkver.so is loaded if needed via LD_PRELOAD for all kind of commands run via the chroot target. This fix PR pkg/32921. Approved by MAINTAINER.
Update to 1.28: - PKG_SYSCONFDIR cannot be set by mk.conf; it is PKG_SYSCONFBASE. This was correct in one place but incorrect in another. Fixes PR pkg/33061 by Yoshito Komatsu.
Update to 1.27: - Allow empty variables to be added to the mk.conf file (useful for, e.g., BINPKG_SITES). Requested by Lans Nordlund in private mail.
Welcome to 1.26: - add MAKEROOT_HOOKS, a whitespace separated list of functions or external scripts to be executed after the sandbox is created, - be more verbose about hooks execution, - run hooks only when they are defined. ok <jmmv>
Add LIBKVER_STANDALONE_PREFIX to _TEMPLATE_VARS so it will appear in the template. (hi seb!)
Pullup ticket 1004 - requested by Stoned Elipot bugfix update for pkg_comp Revisions pulled up: - pkgsrc/pkgtools/pkg_comp/Makefile 1.33 - pkgsrc/pkgtools/pkg_comp/files/pkg_comp.8 1.29 - pkgsrc/pkgtools/pkg_comp/files/pkg_comp.sh 1.27 Module Name: pkgsrc Committed By: seb Date: Fri Jan 6 23:08:51 UTC 2006 Modified Files: pkgsrc/pkgtools/pkg_comp: Makefile pkgsrc/pkgtools/pkg_comp/files: pkg_comp.8 pkg_comp.sh Log Message: Update to version 1.25. Fix libkver support for pkg_comp's build, auto and install targets, Reported broken and fix tested by salo@. Also ensure libkver is built, if needed, even before digest. Approved by jmmv@
Update to version 1.25. Fix libkver support for pkg_comp's build, auto and install targets, Reported broken and fix tested by salo@. Also ensure libkver is built, if needed, even before digest. Approved by jmmv@
Update to version 1.24. When installing libkver, as required when NETBSD_RELEASE is set in a pkg_comp configuration, do so in a special purpose prefix and use it from there. This is useful when running a bulk build in the chroot or simply removing all installed packages in it: the libkver package won't be removed hence the chroot will still be usable. Approved by MAINTAINER.
Update to 1.23: - Sync SETS_X11's default value with recent NetBSD versions: xcontrib.tgz and xmisc.tgz disappeared while xetc.tgz was added, starting in NetBSD 2.0.
Update to 1.22: - Honour INSTALL_PACKAGES during the 'auto' target. Found by jwise@.
Update to 1.21: - Make the EXTRA_MK variable be a list of files rather a single one. From brook at biology.nmsu.edu in PR pkg/30099. - Directly recognize pkg_* commands to be executed within the sandbox (i.e., no need to use the chroot keyword). From Robert Elz in PR pkg/29749. - Fix a typo in the manual page.
fix X tarball names, we no longer have xcontrib.tgz. fixes PR pkg/28608 from Ulrich Heilmann.
Update to 1.19 (ok'ed by agc@, as we are in a freeze): - Ensure that the first attempt to build pkgtools/digest inside the chroot works by explicitly setting PKGSRC_COMPILER to gcc (pkg_comp assumes NetBSD in lots of places, so this assumption is acceptable). It was failing because it set PKGSRC_COMPILER to the empty string in the environment, which breaks the build.
Update to 1.18: - Make kern-GENERIC.tgz part of the default SETS value, so that we get a kernel inside the chroot. If the user removes it from the list, and no /netbsd file exists after extraction, create an empty /netbsd kernel. This fixes packages that look for a kernel during compilation, like net-snmp. Found by cube@.
Update to 1.17: - Recognize the PKGSRC_COMPILER variable and set it automatically in mk.conf. - Add the REAL_CCACHE variable: if set, the directory pointed by it will be null-mounted inside the chroot in a place known by ccache to store the cache. This is useful to keep it across rebuilds of the sandbox. Idea suggested by gavan@.
s/independant/independent/
Update to 1.16: - Use WRKDIR_BASENAME instead of OBJMACHINE to get a unique name of object directories. This way, multiple jails can use the same pkgsrc tree with write access and get the right obj links. - Fix COPYROOTCFG.
Update to 1.15: - Automatic builds can now be interrupted at any time with CTRL+C and then resumed! (with 'auto resume' from the command line). - MAKE_PACKAGES has been deprecated in favour of two new variables: BUILD_PACKAGES, which tells which packages to build after a 'makeroot' and AUTO_PACKAGES, used during the 'auto' target. - MOUNT_SCRIPT and UMOUNT_SCRIPT have been deprecated in favour of MOUNT_HOOKS and UMOUNT_HOOKS, which take a list of shell functions or external commands to be executed. - /pkg_comp is now symlinked to /p inside the chroot, to make paths simpler when working inside it (i.e., with the 'chroot' target). - security/audit-packages is not installed any more inside the chroot by default. This is not needed to get pkgsrc security checks working. The user can add it to BUILD_PACKAGES for a regular build. - pkgtools/xpkgwedge is not installed any more during a 'makeroot'. pkgsrc handles this automatically when needed, so we let it install the package for us. - Ensure that libkver's library is preloaded when doing builds inside the chroot, so that packages get the right version number in them. - When creating a template file, sort all variables alphabetically. - Several miscellaneous changes in the code: simplification of syntax, addition of comments to functions, cleanup of messages...
Update to 1.14: - Add the AUTO_TARGET variable. This specifies the BUILD_TARGET used during an automated build of packages (i.e., pkg_comp auto), so that one can use 'bin-install'. Suggested by gavan@. - Fix minor bug so that a libkver package is built during makeroot.
Update to 1.13: - Fix detection of outdated pkg_install. The 'grep' failed because the error message shown was recently changed in pkgsrc.
Update to 1.12: * Add the -n flag. When specified, do not install INSTALL_PACKAGES nor MAKE_PACKAGES during the creation of the chroot.
Update to version 1.11 Support pathname to configuration files, support latest libkver and emit the usual BSD_PKG_MK ifdef protection in the generated /etc/mk.conf. Approved by jmmv@.
Update to 1.10: * Sync with audit-packages: use the new pkg-vulnerabilities file. * Check if the version of pkg_install inside the chroot is up to date before building anything. If not, force a rebuild automatically. * Disable all those ugly sync's after fsumount (were added because I had some strange problems, IIRC). You can reenabled them by setting SYNC_UMOUNT=yes in the configuration file.
Update to 1.9: - Introduce two new variables, MOUNT_SCRIPT and UMOUNT_SCRIPT, that let the user specify a script file run after mounting known filesystems and before unmounting them, respectively. Patch by seb@, thanks!
Properly set LD_PRELOAD in the environment so libkver works properly. Pointed out by seb@.
Update to 1.8: - Add the NETBSD_RELEASE variable. This is used to automatically configure pkgtools/libkver inside the chroot so that packages see the right kernel version when issuing calls to sysctl(8). Suggested by seb@. - Turn on emacs editing mode by default in sh/ksh.
Update to 1.7: - Added support for audit-packages. pkg_comp will now automatically setup the vulnerabilities file inside the chroot so that pkgsrc can check for security flaws before building packages. See the USE_AUDIT_PACKAGES variable in the manpage. - Added support for gcc3. pkg_comp will now automatically install the gcc3 compiler inside the chroot and build all packages using it. See the USE_GCC3 variable in the manpage. - The new MKCONF_VARS variable lets you add any variable to the generated mk.conf file from the configuration file (no need for EXTRAMK in most cases). - Deprecated the removepkgs target. It was buggy and difficult to adapt to the new changes. removeroot+makeroot should produce the same effect. - Some code cleanup, specially regarding to template file generation and default values for variables. (See next change item) - Configuration file semantics have changed. Variables are now set to their default value if they are NOT set in the configuration file. This changes the behaviour of SETS_X11 specially, which needs to be explicitly set to "no" to disable X11. - Fixed shell profile configuration. Now PS1 is properly set when using the "chroot" target.
Update pkg_comp to 1.6: - Allow the user to issue any command inside the chroot environment using the "chroot" target, instead of only running ROOTSHELL. Patch provided by seb.
Update pkg_comp to 1.5. Fixes: - Check if all sets exist before extracting any of them. - Treat EXTRAMK properly: only process the variable if it is non-empty.
Update pkg_comp to 1.4:
- Added an EXTRAMK variable to allow the addition of any kind of stuff
into the generated mk.conf.
- While creating the template, quote ${LOCALBASE} so it does not get
replaced. Reported by Douglas Brebner in PR pkg/19509.
Update pkg_comp to 1.3: - Added ability to tune LOCALBASE and PKG_SYSCONFBASE. - Deprecated PTHREAD_TYPE variable, not useful any more. - Multiple error checking (directory presence) added. - Several bugfixes (specially in removepkgs target). - Replaced "echo -n" with "printf" (more portable). - Replaced "! -z" with "-n" when doing tests. - Changed my email address to the NetBSD one.
Quote $? variable in a here document, so it is not expanded during its generation. Pointed out by Stoned Elipot. Bump version to 1.2.
Initial import of pkg_comp-1.0, a utility that allows retargetable package building in chrooted environments. Provided in PR pkg/17986 by Julio Merino <jmmv@hispabsd.org>
Initial revision