OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-re Date: 31-Jul-2003 10:22:07
Branch: HEAD Handle: 2003073109220600
Modified files:
openpkg-re news.txt upgrade.txt
Log:
general notes
Summary:
Revision Changes Path
1.20 +8 -0 openpkg-re/news.txt
1.7 +30 -4 openpkg-re/upgrade.txt
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-re/news.txt
============================================================================
$ cvs diff -u -r1.19 -r1.20 news.txt
--- openpkg-re/news.txt 30 Jul 2003 12:17:54 -0000 1.19
+++ openpkg-re/news.txt 31 Jul 2003 08:22:06 -0000 1.20
@@ -1,4 +1,12 @@
+ General Note
+ ============
+
+ o This file news.txt file talks about new features and major
+ improvements. To receive information about tweaks and quirks when
+ upgrading, common pitfalls and ways to bypass them read the
+ companion upgrade.txt document.
+
Major changes between OpenPKG 1.2 and OpenPKG 1.3
=================================================
@@ .
patch -p0 <<'@@ .'
Index: openpkg-re/upgrade.txt
============================================================================
$ cvs diff -u -r1.6 -r1.7 upgrade.txt
--- openpkg-re/upgrade.txt 30 Jul 2003 12:17:01 -0000 1.6
+++ openpkg-re/upgrade.txt 31 Jul 2003 08:22:06 -0000 1.7
@@ -1,9 +1,35 @@
- General Note
- ============
+ General Notes
+ =============
- You cannot skip a version. That means, upgrading from 0.9 to 1.1
- requires an upgrade to 1.0 as an intermediate step.
+ o This file upgrade.txt file talks about tweaks and quirks when
+ upgrading. It lists common pitfalls and ways to bypass them. To
+ receive information about new features and major improvements read
+ the companion news.txt document.
+
+ o You cannot skip a version. That means, upgrading from 0.9 to 1.1
+ requires an upgrade to 1.0 as an intermediate step.
+
+ o Be aware that both major and minor OpenPKG upgrades might introduce
+ a new world order and are subject to change the OpenPKG experience
+ in an incompatible way. Any possible damage could have been done to
+ any piece of the system including, but not limited to, packages
+ being split, consolidated or renamed, packages being replaced with
+ updated vendor versions. In rare cases packages might have be
+ removed and no upgrade path exists at all. Package options and rc
+ variables might have been changed. OpenPKG itself might provide new
+ and incompatible modifications, obsolete parts might have been
+ removed. Do not expect a OpenPKG instance can be upgraded by just
+ building and upgrading every package and everything continues to run
+ without manual adjustments.
+
+ o In contrast, OpenPKG security updates are designed to be drop-in
+ replacements and usually require little or no brain work. They
+ appear after a release was done. That's why they are not discussed
+ here. Please keep in mind that any new release raises the bar of
+ security compatiblity as we only support the latest release and it's
+ immediate successor. So don't fall behind by running outdated
+ releases for prolonged times.
Upgrade from OpenPKG 1.2 to OpenPKG 1.3
=======================================
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
