[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2022-05-08T20:26:52Z 2022-05-08T20:26:52Z schmonz schmonz@pkgsrc.org 2022-05-08T20:26:52Z urn:sha1:bb762b41d5514fdea64b2bfcce994b88d6b71471 PKGREVISION. 2021-10-26T11:11:07Z nia nia@pkgsrc.org 2021-10-26T11:11:07Z urn:sha1:07157b2662ea5afc9c4be6af66ca4ad64928247b All checksums have been double-checked against existing RMD160 and SHA512 hashes 2021-10-07T14:46:45Z nia nia@pkgsrc.org 2021-10-07T14:46:45Z urn:sha1:3f4b0899e43221ea4f34c2e332bfc0f48c7a2cf8 2019-01-14T10:53:37Z jmmv jmmv@pkgsrc.org 2019-01-14T10:53:37Z urn:sha1:098759d7d57ae12ba306807f61b26bdbd5613ed8 Changes in version 2.1 ====================== **Released on 2019-01-14.** * Issue 3: Added a new `PBULK_LOG` setting to point at a location that holds all build logs, and made the `build` command print out details about such logs on success and failure. * Issue 4: Fixed the installable bootstrap kit generated during a build to not leak pkg_comp-internal paths. * Issue 10: Fixed generation of pkg_summary so that it includes all packages and not only those that were explicitly given to the `auto` or `build` commands after a clean rebuild of the sandbox. * PR 20: Fixed the default Git repository from jsonn's to NetBSD's as it has moved upstream. * Added a new `PKG_DEVELOPER` setting to enable pkgsrc development from within the sandbox. 2017-12-09T20:55:48Z jmmv jmmv@pkgsrc.org 2017-12-09T20:55:48Z urn:sha1:9b05c1ddefad734d1d1a243d17854c36c074da56 Problem found by Ian D. Leroux and reported via private email... a few months ago. My bad. 2017-09-02T16:18:56Z jlam jlam@pkgsrc.org 2017-09-02T16:18:56Z urn:sha1:cd09fc6849f4cdf88a3add801a72ff28f6e08d1d Package configuration files should be found in ${PKG_SYSCONFDIR}, which can be modified by a user-settable variable. Look for the default sandboxctl(8) configuration files in ${PKG_SYSCONFDIR.sandboxctl} if that variable is set, or else in ${PKG_SYSCONFBASE}/sandboxctl. Fixes problem noted by Iain Hibbert on tech-pkg@. Bump the PKGREVISION to 2 due to changes in the binary package if PKG_SYSCONFDIR.pkg_comp is set to a non-default value. 2017-04-26T00:48:14Z jmmv jmmv@pkgsrc.org 2017-04-26T00:48:14Z urn:sha1:9c00146258de9b82af8cd52674f735a77a02aa82 This allows the default configuration in pkg_comp to properly find the default configuration of sandboxctl. Bump PKGREVISION to 1. 2017-02-20T11:15:19Z jmmv jmmv@pkgsrc.org 2017-02-20T11:15:19Z urn:sha1:1e5f36bfbc4a3353df30517bd73564e3e5326a87 Should fix the problems observed in: http://ftp.netbsd.org/pub/pkgsrc/misc/joerg/20170219.1406/meta/report.html 2017-02-17T21:25:46Z jmmv jmmv@pkgsrc.org 2017-02-17T21:25:46Z urn:sha1:bcbc93842ebd9940d58cdc932bfda3daa587b572 **Released on 2017-02-17.** This is the first release of the pkg_comp project as a standalone package. This new release shares no code with previous versions and is not compatible with them. The following are the major differences between pkg_comp 2.0 and all previous releases, which incidentally are the reasons that triggered this rewrite: * Support for multiple platforms. * Use of pbulk to (re)build packages within the sandbox. This results in more reliable incremental builds after pkgsrc updates. * Support for bootstrap, generating binary kits as part of the builds. * Better scriptability to allow running from cron(8) trivially. 2017-02-12T10:48:55Z jmmv jmmv@pkgsrc.org 2017-02-12T10:48:55Z urn:sha1:e68acbb19fc234ee91bcbc2cd15e67600452137b 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.