[CVS] OpenPKG: openpkg-web/ faq.wml
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: 09-Mar-2004 22:12:00 Branch: HEAD Handle: 200403092112 Modified files: openpkg-web faq.wml Log: mention /etc/openpkg Summary: RevisionChanges Path 1.45+4 -0 openpkg-web/faq.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.44 -r1.45 faq.wml --- openpkg-web/faq.wml 27 Feb 2004 15:20:27 - 1.44 +++ openpkg-web/faq.wml 9 Mar 2004 21:12:00 - 1.45 @@ -380,6 +380,10 @@ startup. Remember that packages can always be 'deactivated' and started or stopped manually as well. p + liOpenPKG 2.0 and later log their prefix into file + /etc/openpkg. This allows inventory mechanisms to find + all instances installed on a machine. + p liNaturally, OpenPKG will take space in the file system corresponding to the prefix given during the first bootstrap stage. /ol @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: 27-Feb-2004 16:20:28
Branch: HEAD Handle: 2004022715202700
Modified files:
openpkg-web faq.wml
Log:
style and cosmetics
Summary:
RevisionChanges Path
1.44+11 -4 openpkg-web/faq.wml
patch -p0 '@@ .'
Index: openpkg-web/faq.wml
$ cvs diff -u -r1.43 -r1.44 faq.wml
--- openpkg-web/faq.wml 28 Nov 2003 14:19:19 - 1.43
+++ openpkg-web/faq.wml 27 Feb 2004 15:20:27 - 1.44
@@ -7,19 +7,26 @@
This is a list of frequently asked questions and answers about OpenPKG.
+style type=text/css
+OL.faq{ list-style-type: square; padding-left: 20px; }
+OL.faq LI { margin: 0px; margin-top: 2.8px; }
+OL.faq LI DIV { margin-top: 4px; }
+/style
+
define-tag faq endtag=required
preserve id title
set-var %attributes
p
lia name=get-var idbget-var title/b/a
[a href=#get-var idA/a]
-p
+div
%body
+/div
/li
restore id title
/define-tag
-ol
+ol class=faq
faq id=why-openpkg
title=Is OpenPKG useful for me?
@@ -432,8 +439,8 @@
faq id=uid-security
title=What is the fuzz about those multiple user/group ids in OpenPKG?
-Starting with OpenPKG 1.1 the bootstrapping package (openpkg) uses
-four distinct Unix user/group id pairs, previous versions used only two.
+Starting with OpenPKG 1.1, the bootstrapping package (openpkg) uses
+four distinct Unix user/group id pairs (previous versions used only two).
p
box bdwidth=1 bdcolor=#a5a095 bdspace=10 bgcolor=#e5e0d5
pre
@@ .
__
The OpenPKG Projectwww.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: RevisionChanges 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 - 1.42 +++ openpkg-web/faq.wml 28 Nov 2003 14:19:19 - 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 Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
OpenPKG CVS Repository http://cvs.openpkg.org/ Server: cvs.openpkg.org Name: Michael van Elst Root: /e/openpkg/cvs Email: [EMAIL PROTECTED] Module: openpkg-web Date: 14-Aug-2003 19:21:09 Branch: HEAD Handle: 2003081418210900 Modified files: openpkg-web faq.wml Log: reflect change in macro name (with_cc - use_cc) Summary: RevisionChanges Path 1.41+2 -2 openpkg-web/faq.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.40 -r1.41 faq.wml --- openpkg-web/faq.wml 7 Aug 2003 14:46:09 - 1.40 +++ openpkg-web/faq.wml 14 Aug 2003 17:21:09 - 1.41 @@ -503,10 +503,10 @@ %l_cc/usr/local/bin/gcc/pre p Alternatively, you can override tt%l_cc/tt for a single rebuild - by defining with_cc. + by defining use_cc. p pre -.../rpm --define with_cc /usr/local/bin/gcc --rebuild .../pre +.../rpm --define use_cc /usr/local/bin/gcc --rebuild .../pre /faq faq id=perl-gcc @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
Re: [CVS] OpenPKG: openpkg-web/ faq.wml
On Tue, Jul 29, 2003, Ralf S. Engelschall wrote: Server: cvs.openpkg.org Name: Ralf S. Engelschall Root: /e/openpkg/cvs Email: [EMAIL PROTECTED] Module: openpkg-web Date: 29-Jul-2003 20:52:12 Branch: HEAD Handle: 2003072919521200 Modified files: openpkg-web faq.wml Log: one entry obsoleted by OpenPKG 1.3, two new added for answering new things [...] -faq id=why-compress I would prefer we keep those items as they could have been referenced in a archived mailing list which is. Verified to be true in this case. -- [EMAIL PROTECTED] Development Team, Operations Northern Europe, Cable Wireless __ The OpenPKG Projectwww.openpkg.org Developer Communication List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: 12-Jul-2003 21:38:24 Branch: HEAD Handle: 2003071220382400 Modified files: openpkg-web faq.wml Log: typo Summary: RevisionChanges Path 1.38+1 -1 openpkg-web/faq.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.37 -r1.38 faq.wml --- openpkg-web/faq.wml 12 Jul 2003 11:50:04 - 1.37 +++ openpkg-web/faq.wml 12 Jul 2003 19:38:24 - 1.38 @@ -616,7 +616,7 @@ The intention is that those packages are fully equal and compatible from the semantical point of view of the virtual target, but although bany can be chosen/b, only bone should -be used/b (ttfoo/tt). Only bonly is supported/b +be used/b (ttfoo/tt). Only bone is supported/b (ttfoo/tt) and exists for regular usage, while the others (ttfooX/tt) exists for temporary backward compatibility, upgrade preparation or bleeding edge testing reasons only. @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: 02-Apr-2003 17:44:57
Branch: HEAD Handle: 2003040216445700
Modified files:
openpkg-web faq.wml
Log:
we can query names and ids
Summary:
RevisionChanges Path
1.29+2 -1 openpkg-web/faq.wml
patch -p0 '@@ .'
Index: openpkg-web/faq.wml
$ cvs diff -u -r1.28 -r1.29 faq.wml
--- openpkg-web/faq.wml 2 Apr 2003 13:06:00 - 1.28
+++ openpkg-web/faq.wml 2 Apr 2003 15:44:57 - 1.29
@@ -456,10 +456,11 @@
/faq
faq id=uid-query
- title=How can i query OpenPKG RPM to see which user/group ids are used?
+ title=How can i query OpenPKG RPM to see which user/group names/ids are
used?
pre
for i in s m r n; do
rpm --eval ${i}usr=%{l_${i}usr}, ${i}grp=%{l_${i}grp}
+rpm --eval ${i}uid=%{l_${i}uid}, ${i}gid=%{l_${i}gid}
done
/pre
/faq
@@ .
__
The OpenPKG Projectwww.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: 26-Feb-2003 09:38:15 Branch: HEAD Handle: 2003022608381400 Modified files: openpkg-web faq.wml Log: split off overriding-cc from overriding-cflags and enhance both Summary: RevisionChanges Path 1.25+19 -4 openpkg-web/faq.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.24 -r1.25 faq.wml --- openpkg-web/faq.wml 26 Feb 2003 08:18:21 - 1.24 +++ openpkg-web/faq.wml 26 Feb 2003 08:38:14 - 1.25 @@ -454,11 +454,26 @@ faq id=overriding-cflags title=How can i override the CFLAGS default for all packages? - You should be able to achieve this by overriding the l_cc and l_cflags - variables in your tt~/.rpmmacros/tt, i.e. + You can override the RPM default of tt%l_cflags/tt permanently in your + tt~/.rpmmacros/tt. Example: pre - %l_cc gcc - %l_cflags -pipe -O3 -march=i686 -funroll-loops + %l_cflags-pipe -O3 -march=i686 -funroll-loops + /pre +/faq + +faq id=overriding-cc + title=How can i override the CC default for all packages? + You can override the RPM default tt%l_cc/tt permanently in your + tt~/.rpmmacros/tt. This is especially useful when bootstrapping + platforms where OpenPKG does not initially find a C compiler in the + path. The most prominent example is Solaris. Example: + pre + %l_cc/usr/local/bin/gcc + /pre + Alternatively, you can override tt%l_cc/tt for a single rebuild + by defining with_cc. + pre + .../rpm --define with_cc /usr/local/bin/gcc --rebuild ... /pre /faq /ol @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: 26-Feb-2003 09:53:11 Branch: HEAD Handle: 2003022608531100 Modified files: openpkg-web faq.wml Log: perl-gcc Summary: RevisionChanges Path 1.26+11 -0 openpkg-web/faq.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.25 -r1.26 faq.wml --- openpkg-web/faq.wml 26 Feb 2003 08:38:14 - 1.25 +++ openpkg-web/faq.wml 26 Feb 2003 08:53:11 - 1.26 @@ -476,5 +476,16 @@ .../rpm --define with_cc /usr/local/bin/gcc --rebuild ... /pre /faq + +faq id=perl-gcc + title=Why does perl require gcc at run-time? + The build-time of a module with XS parts is the run-time of Perl. + Those modules require bexactly/b the C compiler at their + build-time which was previously used at the built-time of perl. + To control C compiler usage in a deterministic way both at perl + build-time and module build-time aka Perl run-time the perl + package has gcc listed as both a ttBuildPreReq/tt and a + ttPreReq/tt. +/faq /ol @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml tutorial.wml
OpenPKG CVS Repository http://cvs.openpkg.org/ Server: cvs.openpkg.org Name: Michael Schloh Root: /e/openpkg/cvs Email: [EMAIL PROTECTED] Module: openpkg-web Date: 15-Jan-2003 12:12:27 Branch: HEAD Handle: 2003011511122600 Modified files: openpkg-web faq.wml tutorial.wml Log: Update supported platforms, correcting conflicting information. Summary: RevisionChanges Path 1.22+13 -10 openpkg-web/faq.wml 1.16+2 -4 openpkg-web/tutorial.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.21 -r1.22 faq.wml --- openpkg-web/faq.wml 15 Jan 2003 09:07:29 - 1.21 +++ openpkg-web/faq.wml 15 Jan 2003 11:12:26 - 1.22 @@ -108,17 +108,20 @@ /faq faq id=os-support - title=Why are currently only the operating systems Solaris, Linux and + title=Why are only the operating systems Solaris, Linux and FreeBSD fully supported? -To begin with, OpenPKG can be used on any unsupported Unix flavors -with just a few changes. However, we promise full support only -to Solaris, Linux and FreeBSD because they are the most popular -server platforms of the customers at Cable amp; Wireless Germany. -Even with this intention, OpenPKG has been ported and tested on -additional Unix platforms, including Tru64, HP-UX, OpenBSD, NetBSD, -etc. These additional platforms are not fully supported however, -because the resources needed to ensure correct package builds for -them are exhausted. +To begin with, OpenPKG works on a number of other Unix variants. It +can further be patched with small changes to work on an even larger +set of Unix variants. However, we promise full support only to +Solaris, Linux and FreeBSD because they are the most popular server +platforms of the customers at Cable amp; Wireless Germany. As is +clear from the detailed online documentation, OpenPKG users enjoy a +level of partial support for NetBSD, OpenBSD, Tru64, and HP-UX as +well. A quick read through the mailing list archive shows that efforts +are undergoing or have been made to port OpenPKG to Darwin, AIX, IRIX, +and Cygwin. These additional platforms are not fully supported +however, because the resources needed to ensure correct package builds +at OpenPKG central are simply not sufficient. /faq faq id=openpkg-rpm-with-vendor-rpm @@ . patch -p0 '@@ .' Index: openpkg-web/tutorial.wml $ cvs diff -u -r1.15 -r1.16 tutorial.wml --- openpkg-web/tutorial.wml 4 Oct 2002 15:42:12 - 1.15 +++ openpkg-web/tutorial.wml 15 Jan 2003 11:12:26 - 1.16 @@ -21,10 +21,8 @@ ptable trtdiarch-os/inbsp;/tdtduiplatform/i/unbsp;/tdtdbuname -m -r -s/bnbsp;/td/tr -trtdix86-freebsd4.6nbsp;/tdtdFreeBSD 4.6nbsp;/tdtdFreeBSD 4.6-STABLE i386nbsp;/td/tr -trtdsparc64-solaris2.8nbsp;/tdtdSun Solaris 8nbsp;/tdtdSunOS 5.8 sun4unbsp;/td/tr +trtdix86-freebsd4.7nbsp;/tdtdFreeBSD 4.7nbsp;/tdtdFreeBSD 4.7-STABLE i386nbsp;/td/tr trtdsparc64-solaris2.9nbsp;/tdtdSun Solaris 9nbsp;/tdtdSunOS 5.9 sun4unbsp;/td/tr -trtdix86-linux2.2nbsp;/tdtdDebian GNU/Linux 2.2nbsp;/tdtdLinux 2.2.20 i686nbsp;/td/tr trtdix86-linux2.4nbsp;/tdtdDebian GNU/Linux 3.0nbsp;/tdtdLinux 2.4.19 i686nbsp;/td/tr trtdix86-linux2.4nbsp;/tdtdRedHat 7.2nbsp;/tdtdLinux 2.4.9-21 i686nbsp;/td/tr /table/p @@ -33,7 +31,7 @@ successfully ported and tested on many other Unix platforms. There is a high probability that your particular platform is also supported, especially if yours is a recent version of a major Unix platform such as BSD, Linux, Solaris, -Tru64, or HP/UX. +Tru64, or HP-UX. p Additionally make sure you have root access to your system. Although not @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: 13-Jan-2003 14:58:22 Branch: HEAD Handle: 2003011313582100 Modified files: openpkg-web faq.wml Log: add why-compress to FAQ Summary: RevisionChanges Path 1.16+23 -2 openpkg-web/faq.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.15 -r1.16 faq.wml --- openpkg-web/faq.wml 6 Jan 2003 09:52:59 - 1.15 +++ openpkg-web/faq.wml 13 Jan 2003 13:58:21 - 1.16 @@ -31,7 +31,7 @@ packages only. /faq -faq id=about-logo +faq id=about-logo title=Is there background information available on the project name and logo? Yes, OpenPKG (pronounced open-pee-kay-chee) is short for Open Source Software Packages. And the logo shows a package containing @@ -42,7 +42,7 @@ website design. /faq -faq id=why-rpm +faq id=why-rpm title=Why is RPM used and not any other packaging tool? We evaluated lots of existing software building and packaging tools like Debian's dpkg/apt pair, the FreeBSD's ports and their @@ -378,6 +378,27 @@ For the remaining packages, you have to add a patch file to the package which fixes your particular platform problems. /ol +/faq + +faq id=why-compress + title=Why does the OpenPKG bootstrap uses %22compress%22 data format? +The openpkg*src.sh bootstrap should run on as many platforms as +possible. All platforms within the scope of OpenPKG support +unpacking of data that comes in compress format. This is true for +very old but still in production UNIX systems. It is also true for +very new LINUX systems which do not have an uncompress tool +installed by default but come with a bunzip which can unpack +compress format and is detected and used by the bootstrap. There +is no other packed data format with equal availability. +p +When a user creates a openpkg-*.arch-os-hierarchy.sh the resulting +script should be in compress format as well. This was the case in +OpenPKG v1.0 and v1.1 and CURRENT until 20030110 and required the +availablity of a compress tool to the user. As described above, +the latest incarnations of LINUX omit that crucial tool and bzip +cannot create compress data format. For this reason we decided to +drop support for packing openpkg-*.arch-os-hierarchy.sh entirely +beginning with CURRENT 20030113 and OpenPKG v1.2. /faq /ol @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web/ faq.wml
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: 13-Jan-2003 15:34:39 Branch: HEAD Handle: 2003011314343800 Modified files: openpkg-web faq.wml Log: improve why-compress and mix in rse collision Summary: RevisionChanges Path 1.18+24 -22 openpkg-web/faq.wml patch -p0 '@@ .' Index: openpkg-web/faq.wml $ cvs diff -u -r1.17 -r1.18 faq.wml --- openpkg-web/faq.wml 13 Jan 2003 14:08:40 - 1.17 +++ openpkg-web/faq.wml 13 Jan 2003 14:34:38 - 1.18 @@ -381,29 +381,31 @@ /faq faq id=why-compress - title=Why does the OpenPKG bootstrap uses %22compress%22 data format? -The ttopenpkg-*.src.sh/tt bootstrap package should run on -as many platforms as possible. All platforms within the scope -of OpenPKG support unpacking of data that comes in traditional -compress(1) format. This is true for very old but still in -production Unix systems. It is also true for very new Linux systems -which do not have an uncompress tool installed by default but -come with at least gunzip(1) which still can unpack the format of -compress(1) and is automatically detected and used by the bootstrap. -There is no other packed data format with equal availability. + title=Why does the OpenPKG bootstrap use \compress\ data format? +The ttopenpkg*.src.sh/tt source bootstrap should run on as +many platforms as possible. All platforms within the scope of +OpenPKG support unpacking of data that comes in compress format. +This is true for very old but still in production UNIX systems. It +is also true for very new LINUX systems which do not have an +uncompress(1) tool installed by default but come with a gunzip(1) +which can unpack compress format and is detected and used by the +bootstrap. There is no other packed data format with equal +availability. p -When a user creates an ttopenpkg-*.arch-os-id.sh/tt the -resulting script was in compress format as well in OpenPKG -v1.0 and v1.1 and CURRENT until 20030110 and. This required -the availablity of compress(1) to the end-user. Unfortunately, -as mentioned above, the latest incarnations of Linux omit -that crucial tool and gzip(1) cannot create the compress(1) -compatible data format. For this reason we droped compression -in the packing of ttopenpkg-*.arch-os-id.sh/tt entirely -beginning with CURRENT 20030113 and OpenPKG v1.2. For building the -ttopenpkg-*.src.sh/tt file, compress(1) is still required. -But this build step is a developer only step where the extra -installation of compress(1) is accepted. +When a user creates a +ttopenpkg-*.iarch/i-ios/i-ihierarchy/i.sh/tt +binary bootstrap the resulting script was in compress format in +OpenPKG v1.0, v1.1 and CURRENT until 20030110. This required the +availablity of compress(1) to the user. As described above, the +latest incarnations of LINUX omit that crucial tool and gzip(1) is +not a full featured replacement as it cannot create compress +format. For this reason we dropped compression for binary bootstrap +entirely beginning with CURRENT 20030113 and OpenPKG v1.2 and now +keep the data verbatim. +p +For building the ttopenpkg-*.src.sh/tt file, compress(1) is +still required. But this build step is a developer only step where +the extra installation of compress(1) is accepted. /faq /ol @@ . __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
[CVS] OpenPKG: openpkg-web faq.wml
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: 18-Nov-2002 17:02:46 Branch: HEAD Handle: 2002111816024600 Modified files: openpkg-web faq.wml Log: finally give an answer to this package number question Summary: RevisionChanges Path 1.14+37 -0 openpkg-web/faq.wml Index: openpkg-web/faq.wml $ cvs diff -u -r1.13 -r1.14 faq.wml --- openpkg-web/faq.wml 4 Apr 2002 14:06:32 - 1.13 +++ openpkg-web/faq.wml 18 Nov 2002 16:02:46 - 1.14 @@ -313,5 +313,42 @@ involved packages tested in depth, of course. /faq +faq id=num-pkgs + title=Compared to the 7000 packages in FreeBSD and 9000 packages in Debian GNU/Linux +the 400 packages OpenPKG provides look rather tiny? +If you compare just the number of packages, this is correct. +But you are comparing apples with pears here, because: +p +ol + liFreeBSD and Debian usually package ieverything/i, although + 90% of the packaged software are just neat toys and far away from + killer applications. OpenPKG is the other way round: 90% are + formed by essential packages only and just the remainder are toys. + p + liFreeBSD and Debian provide packaged software for all types + of deployment, ranging from stripped-down embedded devices, over + networking servers, up to colorful desktops with all bells and + whistles. OpenPKG mainly focuses on deployment on network servers + and up to now has just a few desktop-related packages. If you + really want to deploy software in non-server situations you should + not focus on OpenPKG, please. Then please stick with the packages + of other vendors which focus on your situation. + p + liFreeBSD and Debian usually package all variants, versions and + alternatives of a piece of software. For instance, they provide + dozens of possible shells while OpenPKG mainly just provides the + most popular ones (bash, ksh, tcsh, zsh). Additionally, they + package very often multiple vendor versions (stable, development, + snapshot, etc) while OpenPKG most of the time provides only a + single version. + /ol + p + All those points together result in the dramatically different + numbers of packages. But it is wrong if you think the lower number of + packages would mean OpenPKG is incomplete. OpenPKG actually provides + far more packages for software than you usually need to deploy on a + server platform. +/faq + /ol __ The OpenPKG Projectwww.openpkg.org CVS Repository Commit List [EMAIL PROTECTED]
