|File: [cvs.NetBSD.org] / pkgsrc / sysutils / sysupgrade / DESCR (download)
Revision 1.1, Mon Aug 6 17:06:17 2012 UTC (2 years, 10 months ago) by jmmv
CVS Tags: pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, pkgsrc-2012Q3-base, pkgsrc-2012Q3, HEAD
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.