In article <a29f3l$j4g$[EMAIL PROTECTED]> you wrote:
> How about special per OS options. THere is no IBM HTTPserver for freebsd
> and I would like to make a spec for php-4.1.1 where it compiles fine on
> solaris and linux with the IBM solaris package installed. Is it ok with the
> openpkg policy to require a external package that is not maintained by
> openpkg ?
In general a dependency to an external package is against the "be
self-containt and stand-alone" policy. Especially if this dependent
stuff is only available on a few platforms. If it is available on at
least FreeBSD, Linux and Solaris our approach usually is to re-package
it (as mentioned) to change the external dependency to an internal one.
The "jdk-sun" and "tsmc" packages are an example.
Nevertheless don't be bothered by those policies. These are just
restrictions to packages which should become official ones and included
into official OpenPKG releases. If you look into our CVS you will
notice that we released only 167 out of 242 packages as OpenPKG 1.0,
because the others are either not tested enough, do not fulfill all
requirements, etc. Nevertheless we packaged it for us.
The same should apply to you. Either just make a local package out of
this, i.e., treat OpenPKG just as the framework to fulfill your local
requirements. Or (if it at least fulfills most of the policies and is
useful to others, too) send it to us for inclusing into the forthcoming
contributor area (more details later).
> And, where do I send the changes so that others can use it as
> well ?
We will establish a contributor area in the FTP and CVS services of
OpenPKG. You then can upload your changes and contributions there. Until
this is established, just send your stuff either to the bug database or
post it on openpkg-dev.
> How about packages that only work on certain OS'es ?
> and
> How about wrappers for commercial packages ?
That's a problem, because this is against OpenPKG cross-platform policy.
At least FreeBSD, Linux and Solaris have to work. If this is the case,
no problem. If not, it should to be perhaps re-thought whether the
package is worth to be packaged. Because usually all good Open Source
software should be portable to these three platforms. And the commercial
software usually is not worth packaging inside OpenPKG because it has
too much special external dependencies to the particular platform and is
usually only available as binary.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
