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 ? And, where do I send the changes so that others can use it as well ? How about packages that only work on certain OS'es ? and How about wrappers for commercial packages ?
Hopw not to create the in german so famous wholes in the belly ... cheers Michael Ralf S. Engelschall wrote: > > In article <[EMAIL PROTECTED]> you wrote: > >> [...] >> We prefer the clean-room approach and did not care about existing >> .spec's at all. We always start from scratch, because experience >> showed that you are faster this way if you want to reach a 100% clean >> packaging. The are multiple reasons for this. The main ones follow: >> >> 1. OpenPKG packages _have to_ be build-able under non-root >> (for security and OS-trashing reasons) >> >> 2. OpenPKG packages _have to_ be build-able inside $RPM_BUILD_ROOT >> (for correct file determination reasons) >> >> 3. OpenPKG package specifications _have to_ be all of the >> same coding style. We're very pedantic about cleanness. >> (for maintainance and consistency reasons) > > Just FYI: This is now answered in even more detail also in the FAQ. > > Ralf S. Engelschall > [EMAIL PROTECTED] > www.engelschall.com > ______________________________________________________________________ > The OpenPKG Project www.openpkg.org > User Communication List [EMAIL PROTECTED] ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
