OpenPKG CVS Repository
http://cvs.openpkg.org/
____________________________________________________________________________
Server: cvs.openpkg.org Name: Ralf S. Engelschall
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-web Date: 06-Jan-2003 10:53:00
Branch: HEAD Handle: 2003010609525900
Modified files:
openpkg-web faq.wml
Log:
answer the porting question
Summary:
Revision Changes Path
1.15 +30 -0 openpkg-web/faq.wml
____________________________________________________________________________
patch -p0 <<'@@ .'
Index: openpkg-web/faq.wml
============================================================================
$ cvs diff -u -r1.14 -r1.15 faq.wml
--- openpkg-web/faq.wml 18 Nov 2002 16:02:46 -0000 1.14
+++ openpkg-web/faq.wml 6 Jan 2003 09:52:59 -0000 1.15
@@ -350,5 +350,35 @@
server platform.
</faq>
+<faq id="porting"
+ title="How can I port OpenPKG to a new platform?">
+ <p>
+ Porting OpenPKG to a new platform usually is two-fold:
+ <p>
+ <ol>
+ <li>You have to get the bootstrap package "openpkg" building and
+ running on the new platform. This basically means that that the
+ contained software packages (Bash, cURL, Tar, RPM, etc) have to
+ build and that the linking into the system (users/groups and
+ cron/init scripts) is known by the bootstrap. For getting the
+ software building, you perhaps have to add one or more patchfiles
+ to the "openpkg" package or at least use some "shtool"
+ substitutions in "openpkg.spec". For the linking into the system,
+ add the corresponding commands to the "%pre" and "%preun" sections
+ of "openpkg.spec".
+ <p>
+ <li>You have to port your wished OpenPKG packages to the new platform.
+ Because all OpenPKG packages are inherently portable (because
+ do not contain any platform specific things), porting them
+ usually always means to get the underlying vendor software
+ package building. OpenPKG most of the time (only a few exceptions
+ exists) package only already portable vendor software. So
+ as long as your new platform provides a fair amount of the POSIX
+ APIs, mostly all OpenPKG packages will work out of the box.
+ For the remaining packages, you have to add a patch file
+ to the package which fixes your particular platform problems.
+ </ol>
+</faq>
+
</ol>
@@ .
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
