kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/sysutils/sysbuild/PLIST

16 lines
436 B
Text
Raw Normal View History

Update to 2.7: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysbuild is now a first-class package and includes a traditional build system based on automake and autoconf.
2013-07-29 01:32:58 +02:00
@comment $NetBSD: PLIST,v 1.8 2013/07/28 23:32:58 jmmv Exp $
Initial (re)addition of sysbuild, version 2.0: sysbuild is a tool to automate the maintenance of the NetBSD sources and the build of releases by means of a single command and a configuration file that tells sysbuild what to do. Since NetBSD 1.6 (released on July 2011), the source tree has included a very flexible script (build.sh) to build a full NetBSD release for the current platform or to cross-build for any of the supported platforms. The flipside of the flexibility is that the script is inconvenient to use on a daily basis because of the myriad of options it takes. Furthermore, managing the source trees that make up NetBSD is not in the scope of build.sh: the user must fetch these trees and keep them up to date by hand. While these details are all fine on their own, rebuilding NetBSD frequently (to keep a system up to date, or just for development tasks) is convoluted. Developers and users usually find themselves writing their own wrapper scripts over build.sh to simplify their daily tasks. sysbuild extends build.sh by adding support for configuration files and source tree management, allowing NetBSD rebuilds with a single and simple command. Make sure to check the sysbuild-user package for a way to trivially set up periodic NetBSD rebuilds under an dedicated, unprivileged user. This is version 2.0 because sysbuild already existed 10 years ago. It served the same purpose, but it was removed because it stopped working with NetBSD 2.0 (can't remember why though). Also, I'm convinced the previous implementation was quite bad.
2012-07-25 14:18:22 +02:00
bin/sysbuild
bin/sysbuild4cron
man/man1/sysbuild.1
man/man1/sysbuild4cron.1
Update to 2.4: - Add a MKVARS variable to pass arbitrary variables to build.sh through -V. E.g. MKVARS="MKDEBUG=yes". - Move the documentation of the configuration file to a new sysbuild.conf(5).
2012-10-13 20:40:33 +02:00
man/man5/sysbuild.conf.5
Update to 2.7: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysbuild is now a first-class package and includes a traditional build system based on automake and autoconf.
2013-07-29 01:32:58 +02:00
share/doc/sysbuild/AUTHORS
share/doc/sysbuild/COPYING
share/doc/sysbuild/NEWS
share/doc/sysbuild/README
Initial (re)addition of sysbuild, version 2.0: sysbuild is a tool to automate the maintenance of the NetBSD sources and the build of releases by means of a single command and a configuration file that tells sysbuild what to do. Since NetBSD 1.6 (released on July 2011), the source tree has included a very flexible script (build.sh) to build a full NetBSD release for the current platform or to cross-build for any of the supported platforms. The flipside of the flexibility is that the script is inconvenient to use on a daily basis because of the myriad of options it takes. Furthermore, managing the source trees that make up NetBSD is not in the scope of build.sh: the user must fetch these trees and keep them up to date by hand. While these details are all fine on their own, rebuilding NetBSD frequently (to keep a system up to date, or just for development tasks) is convoluted. Developers and users usually find themselves writing their own wrapper scripts over build.sh to simplify their daily tasks. sysbuild extends build.sh by adding support for configuration files and source tree management, allowing NetBSD rebuilds with a single and simple command. Make sure to check the sysbuild-user package for a way to trivially set up periodic NetBSD rebuilds under an dedicated, unprivileged user. This is version 2.0 because sysbuild already existed 10 years ago. It served the same purpose, but it was removed because it stopped working with NetBSD 2.0 (can't remember why though). Also, I'm convinced the previous implementation was quite bad.
2012-07-25 14:18:22 +02:00
share/examples/sysbuild/default.conf
Update to 2.3: - Added the 'env' command. This prints a small shell snippet that can be imported into the current shell. The printed code defines a set of convenience global variables and functions to work with the source tree.
2012-08-25 21:20:53 +02:00
share/sysbuild/env.sh
Initial (re)addition of sysbuild, version 2.0: sysbuild is a tool to automate the maintenance of the NetBSD sources and the build of releases by means of a single command and a configuration file that tells sysbuild what to do. Since NetBSD 1.6 (released on July 2011), the source tree has included a very flexible script (build.sh) to build a full NetBSD release for the current platform or to cross-build for any of the supported platforms. The flipside of the flexibility is that the script is inconvenient to use on a daily basis because of the myriad of options it takes. Furthermore, managing the source trees that make up NetBSD is not in the scope of build.sh: the user must fetch these trees and keep them up to date by hand. While these details are all fine on their own, rebuilding NetBSD frequently (to keep a system up to date, or just for development tasks) is convoluted. Developers and users usually find themselves writing their own wrapper scripts over build.sh to simplify their daily tasks. sysbuild extends build.sh by adding support for configuration files and source tree management, allowing NetBSD rebuilds with a single and simple command. Make sure to check the sysbuild-user package for a way to trivially set up periodic NetBSD rebuilds under an dedicated, unprivileged user. This is version 2.0 because sysbuild already existed 10 years ago. It served the same purpose, but it was removed because it stopped working with NetBSD 2.0 (can't remember why though). Also, I'm convinced the previous implementation was quite bad.
2012-07-25 14:18:22 +02:00
${TESTS}tests/sysbuild/Kyuafile
${TESTS}tests/sysbuild/sysbuild_test
${TESTS}tests/sysbuild/sysbuild4cron_test
Reference in a new issue Copy permalink