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

43 lines
1.1 KiB
Makefile
Raw Normal View History

Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.
2014-10-09 16:05:50 +02:00
# $NetBSD: Makefile,v 1.9 2014/10/09 14:07:00 wiz Exp $
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
Update to 1.5: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysupgrade is now a first-class package and includes a traditional build system based on automake and autoconf. * Moved the sysupgrade script from bin to sbin.
2013-07-29 01:37:14 +02:00
DISTNAME= sysupgrade-1.5
Depend on atf 0.20 (not atf-libs) and bump PKGREVISION.
2014-02-08 16:59:30 +01:00
PKGREVISION= 1
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
CATEGORIES= sysutils
Update to 1.5: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysupgrade is now a first-class package and includes a traditional build system based on automake and autoconf. * Moved the sysupgrade script from bin to sbin.
2013-07-29 01:37:14 +02:00
MASTER_SITES= https://github.com/jmmv/sysupgrade/releases/download/sysupgrade-1.5/
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
MAINTAINER= jmmv@NetBSD.org
COMMENT= Automate upgrades of NetBSD
LICENSE= modified-bsd
Update to 1.5: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysupgrade is now a first-class package and includes a traditional build system based on automake and autoconf. * Moved the sysupgrade script from bin to sbin.
2013-07-29 01:37:14 +02:00
GNU_CONFIGURE= yes
TEST_TARGET= check
USE_LANGUAGES= # empty
USE_TOOLS= pkg-config
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
BUILD_DEFS+= VARBASE
Update to 1.5: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysupgrade is now a first-class package and includes a traditional build system based on automake and autoconf. * Moved the sysupgrade script from bin to sbin.
2013-07-29 01:37:14 +02:00
SYSUPGRADE_CACHEDIR= ${VARBASE}/cache/sysupgrade
OWN_DIRS= ${SYSUPGRADE_CACHEDIR} root wheel
CONFIGURE_ARGS+= SYSUPGRADE_CACHEDIR=${SYSUPGRADE_CACHEDIR}
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
Update to 1.5: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysupgrade is now a first-class package and includes a traditional build system based on automake and autoconf. * Moved the sysupgrade script from bin to sbin.
2013-07-29 01:37:14 +02:00
CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
INSTALL_MAKE_FLAGS+= sysconfdir=${EGDIR}
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
EGDIR= ${PREFIX}/share/examples/sysupgrade
CONF_FILES+= ${EGDIR}/default.conf ${PKG_SYSCONFDIR}/sysupgrade.conf
PKG_OPTIONS_VAR= PKG_OPTIONS.sysupgrade
PKG_SUPPORTED_OPTIONS= tests
PKG_SUGGESTED_OPTIONS= tests
.include "../../mk/bsd.options.mk"
.if $(PKG_OPTIONS:Mtests)
Depend on atf 0.20 (not atf-libs) and bump PKGREVISION.
2014-02-08 16:59:30 +01:00
. include "../../devel/atf/buildlink3.mk"
Update to 1.5: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysupgrade is now a first-class package and includes a traditional build system based on automake and autoconf. * Moved the sysupgrade script from bin to sbin.
2013-07-29 01:37:14 +02:00
PLIST_SUBST+= TESTS=
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
.else
PLIST_SUBST+= TESTS=@comment
.endif
Update to 1.5: Released on 2013-07-28. * Sources migrated to a GitHub project from the previous copy in the pkgsrc repository. sysupgrade is now a first-class package and includes a traditional build system based on automake and autoconf. * Moved the sysupgrade script from bin to sbin.
2013-07-29 01:37:14 +02:00
BUILDLINK_API_DEPENDS.shtk+= shtk>=1.3
Update to 1.1: - Use shtk for the common utilities and configuration file parsing functionality. The local copies of the "config" and "utils" modules are gone.
2012-08-15 23:21:15 +02:00
.include "../../devel/shtk/buildlink3.mk"
Initial addition of sysupgrade, version 1.0: sysupgrade is a script to automate NetBSD system upgrades. sysupgrade works by first fetching distribution sets from a specified site or local directory, then by upgrading the system using such distribution sets and later by ensuring that the system configuration is up to date. All the process is controlled by a configuration file, and the defaults should suit the most common NetBSD upgrades. sysupgrade can be used to perform upgrades across different system major and/or minor versions, and it can also be used to track a stable or development branch from the CVS repository. sysbuild is the perfect companion to sysupgrade in those cases where you want to roll your own binaries: both utilities share a very similar command-line and configuration interface, and the default configuration files provide examples on how to integrate one with the other. A few notes about the import: Right after I submitted sysbuild, I was pointed at etcmanage and its scripts to build and upgrade NetBSD. I am sending this anyway because 1) it matches sysbuild's behavior closely, 2) it has a detailed manual page, 3) it has tests... and, well, 4) I had already written most of it at that time and didn't want to throw it away! The config and utils modules in this import are a duplicate of the code in sysbuild, with a few tweaks. This is really bad and the code should be deduplicated somehow. I'm not sure what the best way of doing so is and can only think about introducing a common base package with the shared code (which brings its own problems). I have tested this to upgrade both -current and 6.0_BETA2 to newer snapshots, both from local and remote release files.
2012-08-06 19:06:17 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink