In article <[EMAIL PROTECTED]> you wrote:
> I Don't know.
> It is one of the basic questions I have, like also if I
> have a package like courier-imap which can have multiple subpackages, do
> we support subpackages or do I make one full for pgsql, one full for
> mysql, one full for ldap .... If we support multiple packaging I would
> hae patched the package to support python in a subpackage and than would
> not have the problem.
Until know we avoid sub-packages, because if you start with this
you very quickly get lots of more packages and this increases the
nightmare of maintaining and keeping those packages up to date. We plan
to introduce sub-packages soon after we got our front-end to "rpm"
(called "openpkg") which does all the package maintainance. Then it
doesn't matter how much packages one needs, because they are fetched
and installed automatically. But until this point (planned around
OpenPKG 1.3) we want to avoid sub-packaging. Because just doing a few
is ugly. Our point of view is that either we do it fully over the whole
system whereever it is useful or we avoid it at all. Anything else is
is inconsistent.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
