Re: openpkg current and perl.req
On Tue, Mar 23, 2004, Bill Campbell wrote:
While working to get my courier-imap package running under release 2.0 with
openpkg from the current tree, I ran into a problem where it failed in
dependency checking looking for the %{l_prefix}/lib/openpkg/perl.req
script. Looking at the openpkg.spec file, this file is explicitly removed
in the %install processing around line 784. It's still referenced though
in the %{l_prefix}/lib/openpkg/macros file.
Yes, because this file is from the original RPM and its content is
overriden by our %{l_prefix}/etc/openpkg/rpmmacros except for features
we do not use in OpenPKG. And you seem to not have AutoPreReq: no in
your .spec, so you are using a RPM feature which is intentionally not
used in OpenPKG.
My general suggestion is to _NEVER_ write an OpenPKG .spec file from
scratch for two reasons:
1. you usually finally want that it is taken over by us into the
official repository, so it has to pass openpkg-dev lint. And this
linting tool you such restrictive that you certainly will not being
able to fulfill its requirements by a from-scratch .spec file.
2. the chance is hight that you are using RPM features which are not
intended to be used in OpenPKG. Or you forget a lot of features
to use which are required in OpenPKG.
So, always use openpkg-dev new for generating a new .spec
from our template (yes, I know there is unfortunately still no
developer/contributor documentation for this) or start from one of the
existing 700 .spec files.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
__
The OpenPKG Projectwww.openpkg.org
Developer Communication List [EMAIL PROTECTED]
Re: openpkg current and perl.req
On Tue, Mar 23, 2004, Ralf S. Engelschall wrote:
On Tue, Mar 23, 2004, Bill Campbell wrote:
While working to get my courier-imap package running under release 2.0 with
openpkg from the current tree, I ran into a problem where it failed in
dependency checking looking for the %{l_prefix}/lib/openpkg/perl.req
script. Looking at the openpkg.spec file, this file is explicitly removed
in the %install processing around line 784. It's still referenced though
in the %{l_prefix}/lib/openpkg/macros file.
Yes, because this file is from the original RPM and its content is
overriden by our %{l_prefix}/etc/openpkg/rpmmacros except for features
we do not use in OpenPKG. And you seem to not have AutoPreReq: no in
your .spec, so you are using a RPM feature which is intentionally not
used in OpenPKG.
Thanks. That cures the immediate problem.
Actually it's ``AutoReq'' and ``AutoReqProv'' which I had copied into most
of my .spec files (and explains why this package always bitched loudly
about dependencies on older version of openpkg :-).
My general suggestion is to _NEVER_ write an OpenPKG .spec file from
scratch for two reasons:
1. you usually finally want that it is taken over by us into the
official repository, so it has to pass openpkg-dev lint. And this
linting tool you such restrictive that you certainly will not being
able to fulfill its requirements by a from-scratch .spec file.
2. the chance is hight that you are using RPM features which are not
intended to be used in OpenPKG. Or you forget a lot of features
to use which are required in OpenPKG.
So, always use openpkg-dev new for generating a new .spec
from our template (yes, I know there is unfortunately still no
developer/contributor documentation for this) or start from one of the
existing 700 .spec files.
As I understand it, the openpkg-dev package is only available via a CVS
checkout. I just spent some time poking around the OpenPKG web site, but
can't find anything about the login procedures for anonymous login and
checkout from the CVS tree.
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/
``Liberty don't work as good in practice as it does in speeches.''
Will Rogers
__
The OpenPKG Projectwww.openpkg.org
Developer Communication List [EMAIL PROTECTED]
Re: openpkg current and perl.req
On Tue, Mar 23, 2004, Bill Campbell wrote: [...] As I understand it, the openpkg-dev package is only available via a CVS checkout. I just spent some time poking around the OpenPKG web site, but can't find anything about the login procedures for anonymous login and checkout from the CVS tree. http://www.openpkg.org/contrib.html On the bottom of the page (Contributor Environment) there is a link to the openpkg-dev script. (mk) -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 Im prämotorischen Cortex kann jeder ein Held sein. (bdw) __ The OpenPKG Projectwww.openpkg.org Developer Communication List [EMAIL PROTECTED]
Re: openpkg current and perl.req
On Tue, Mar 23, 2004, Matthias Kurz wrote: On Tue, Mar 23, 2004, Bill Campbell wrote: [...] As I understand it, the openpkg-dev package is only available via a CVS checkout. [...] Yes via CVS but no need to checkout. I just spent some time poking around the OpenPKG web site, but can't find anything about the login procedures for anonymous login and checkout from the CVS tree. http://www.openpkg.org/contrib.html On the bottom of the page (Contributor Environment) there is a link to the openpkg-dev script. I just added another link to instructions how to setup and use the tool. -- [EMAIL PROTECTED], Cable Wireless __ The OpenPKG Projectwww.openpkg.org Developer Communication List [EMAIL PROTECTED]
