On Wed, Nov 27, 2002, Michael Schloh von Bennewitz wrote:
> >> [...]
> >> Redirect buildfiles as well as installation, add build and runtime
> >> prerequisites, remove unused l_prefix substitution, correct version
> >> substitution, and do not package unused and generated files.
> >> [...]
> >
> > Err... no, I _INTENTIONALLY_ have _NOT_ made it dependent on Perl and
> > Make. That's why I packaged the openpkg.1 and not just openpkg.pod. What
> > you are trying to fix is the @version@. Ok, but not this way, please.
> >
> This package includes perl scripts, just like m4 or openssl. In efforts to
> make OpenPKG as robust and *self contained* as possible, we've always stated
> dependencies explicitly. Is there a good reason that now, we are not stating
> that this (clearly perl-needing) package requires perl? How are we going to
> otherwise know if the external perl is not very old or a custom installation?
>
> You packaged a Makefile, although it was left unused in the packaging. I
> assumed it could be used to work around the version expansion problem copying
> the raw manfile. There are a number of other possible solutions however, none
> of them requiring packaging of the Manfile or a dependency to make.
The point is simply that "openpkg-tool" is a BOOTSTRAPPING package
which is intended to be installed directly after "openpkg". It
officially assumes (perhaps we should write this down in the manual
page!) that "perl" is already available somewhere on the system. If
<prefix>/bin/perl is found, it prefers this, too. But it does not have
an RPM-dependency to "perl", because this would us not allow to use
"openpkg-tool" to install an OpenPKG instance mostly from scratch. Hence
also the wrapper "openpkg", which first tries to find "perl" and if not
found gives out just a message.
The Makefile exists in the source package, because the Makefile
_belongs_ to the sources. It has not to mean that it is _used_ for
building under RPM build-time. Here it is just for developer purposes,
because (for the same reason as above) pod2man cannot be assumed to
be present on "openpkg-tool" build-time. If we would leave out the
"Makefile", people could only work with the "openpkg-tool" sources from
CVS. But the goal is that a source RPM really contains everything needed
for a package. So the Makefile is also included.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
