Up to [cvs.NetBSD.org] / pkgsrc / sysutils / sysupgrade
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: MAIN
Revision 1.6 / (download) - annotate - [select for diffs], Tue Oct 23 19:51:26 2012 UTC (7 months, 3 weeks ago) by asau
CVS Tags: pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, HEAD
Changes since 1.5: +1 -2 lines
Diff to previous 1.5 (colored)
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
Revision 1.5 / (download) - annotate - [select for diffs], Thu Oct 11 00:16:46 2012 UTC (8 months, 1 week ago) by jmmv
Changes since 1.4: +2 -2 lines
Diff to previous 1.4 (colored)
Update to 1.4: - Add support to fetch release sets via ssh.
Revision 1.4 / (download) - annotate - [select for diffs], Fri Sep 7 12:48:32 2012 UTC (9 months, 1 week ago) by jmmv
CVS Tags: pkgsrc-2012Q3-base, pkgsrc-2012Q3
Changes since 1.3: +2 -2 lines
Diff to previous 1.3 (colored)
Update to 1.3: - ftp(1) in NetBSD 1.5.2 does not support using -R on files that do not exist yet. Avoid using this option unless necessary. - httpd(8) in NetBSD 1.5.2 does not support the -P option. Skip the http test unless this option is present, as otherwise we cannot easily kill the spawned httpd instance on a test failure.
Revision 1.3 / (download) - annotate - [select for diffs], Sat Aug 25 01:57:27 2012 UTC (9 months, 3 weeks ago) by jmmv
Changes since 1.2: +2 -2 lines
Diff to previous 1.2 (colored)
Update to 1.2: - Use netbsd-*.gz files to install the kernel rather than kern-*.tgz sets. This lets sysupgrade work in conjunction with the "releasekernel" target of build.sh, as this generates the former instead of the latter. - Preserve timestamps of the kernel when backing it up as onetbsd. - Fix some tests to not rely on the current state of the system (the cache directory and the autodetection of KERNEL).
Revision 1.2 / (download) - annotate - [select for diffs], Wed Aug 15 21:21:15 2012 UTC (10 months ago) by jmmv
Changes since 1.1: +15 -23 lines
Diff to previous 1.1 (colored)
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.
Revision 1.1 / (download) - annotate - [select for diffs], Mon Aug 6 17:06:17 2012 UTC (10 months, 1 week ago) by jmmv
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.
This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.