pkgsrc/sysutils/sysbuild/Makefile

42 lines
1.1 KiB
Makefile
Raw Normal View History

# $NetBSD: Makefile,v 1.27 2014/02/08 15:59:30 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
DISTNAME= sysbuild-2.7
PKGREVISION= 1
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
CATEGORIES= sysutils
MASTER_SITES= https://github.com/jmmv/sysbuild/releases/download/sysbuild-2.7/
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
MAINTAINER= jmmv@NetBSD.org
COMMENT= Automates builds of NetBSD and manages source trees
LICENSE= modified-bsd
PKG_INSTALLATION_TYPES= overwrite pkgviews
GNU_CONFIGURE= yes
TEST_TARGET= check
USE_LANGUAGES= # empty
USE_TOOLS= pkg-config
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
PKG_SYSCONFSUBDIR= sysbuild
CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
CONFIGURE_ARGS+= SYSBUILD_CONFSUBDIR=
INSTALL_MAKE_FLAGS+= sysbuild_confdir=${EGDIR}
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
EGDIR= ${PREFIX}/share/examples/sysbuild
CONF_FILES+= ${EGDIR}/default.conf ${PKG_SYSCONFDIR}/default.conf
PKG_OPTIONS_VAR= PKG_OPTIONS.sysbuild
PKG_SUPPORTED_OPTIONS= tests
PKG_SUGGESTED_OPTIONS= tests
.include "../../mk/bsd.options.mk"
.if $(PKG_OPTIONS:Mtests)
. include "../../devel/atf/buildlink3.mk"
PLIST_SUBST+= TESTS=
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
.else
PLIST_SUBST+= TESTS=@comment
.endif
BUILDLINK_API_DEPENDS.shtk+= shtk>=1.3
.include "../../devel/shtk/buildlink3.mk"
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
.include "../../mk/bsd.pkg.mk"