OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Thomas Lotterer
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 28-Nov-2003 15:19:20
Branch: HEAD Handle: 2003112814191900
Modified files:
openpkg-web faq.wml
Log:
add UPD information
Summary:
Revision Changes Path
1.43 +33 -0 openpkg-web/faq.wml
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/faq.wml
============================================================================
$ cvs diff -u -r1.42 -r1.43 faq.wml
--- openpkg-web/faq.wml 28 Nov 2003 13:46:27 -0000 1.42
+++ openpkg-web/faq.wml 28 Nov 2003 14:19:19 -0000 1.43
@@ -663,5 +663,38 @@
between architecture independent and dependent binary packages.
</faq>
+<faq id="update-where"
+ title="Where can i find packages and information about updates within a
release?">
+ Find updated packages for releases in the UPD directory below
+ the release on the <a href="ftp://ftp.openpkg.org/release/";>FTP
+ Server</a>. Find a brief description for each update
+ in the 00README file beneath the package.
+ Example: <a href="ftp://ftp.openpkg.org/release/1.3/UPD/00README";>
+ release/1.3/UPD/00README</a> file. Find in-depth developer level
+ information by browsing the CVS timeline of the package.
+ Example: <a href="http://cvs.openpkg.org/timeline?px=openpkg-src/openssh";>
+ OpenSSH</a>.
+</faq>
+
+<faq id="update-breakexisting"
+ title="Will updating a package within a release likely break my existing
setup?">
+ While we cannot guarantee this won't it is very unlikely that
+ an update will break an existing setup. In fact, one reason
+ why updates are created is to fix existing problems in the
+ least intrusive and most compatible way. Updates will always
+ include the same vendor version. Sometimes we even preserve bugs
+ intentionally. Most updates are driven by security incidents
+ which come with an advisory describing the problem, scope and
+ required actions to prevent the problem. Please examine our <a
+ href="http://www.openpkg.org/security.html";>security pages</a>. In
+ any case we work hard to make upgrades a no-brainer. Packages are
+ designed to be drop-in replacements for it predecessor(s).
+</faq>
+
+<faq id="update-mutliple"
+ title="What should i do if multiple updates within a release exist?">
+ Our updates are patched full packages. Just take the latest.
+</faq>
+
</ol>
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
