Hello Frank, On Mon, Dec 08, 2003, F. Even wrote: > I'm looking to build Apache with some of the options turned on. Do I need > to specify --define on the --rebuild of the .src.rpm step, or can I specify > that after the binary RPM has been built? ...or, is it when the binary RPM > is built, there are no options that can be specified? > After learning which options a OpenPKG source package supports (with rpm -qpi), you can use those options by specifying the options on the command line while building the source package (rpm --rebuild --define 'with_option yes' package.src.rpm).
Unfortunately while installing binary packages (rpm -Uvh package.ix86.rpm),
you can give all sorts of options on the command line (--define
'with_whatever yes') and rpm will silently ignore them. It's just not
possible to add or remove options after a binary package is created. If you
make a mistake, you'll have to build the source package again using the
correct options.
It's a wise thing to do to check a newly created binary package to make sure
that the options you wish are really there (rpm -qpi package.ix86.rpm). It's
easy to make the mistake of incorrectly specifying the option. For example,
$ rpm --rebuild package.src.rpm --define 'with_x11 yes' (CORRECT!)
$ rpm --rebuild package.src.rpm --define 'with_x11=yes' (WRONG!)
In the second example above, the package will probably be built without X11.
$ rpm -qpi package.ix86.rpm
[...]
Provides:
package::with_x11 = =yes
> ...and I'm left wondering how does the .openpkg folder get created and save
> these build options? I do not have one, and I've installed many packages
> through the process of "rpm --rebuild
> ftp://ftp.openpkg.org/release/1.3/SRC/pkg-name.src.rpm"; and then "rpm
> -Uvh/Fvh pkg-name.rpm" from the /cw/RPM/PKG folder. I have the openpkg-tool
> installed....I really have not seen any good documentation on how to use it
> though....and the man page doesn't seem to really help pull it all together.
>
Today, neither RPM, OpenPKG, nor the openpkg-tool creates the folder
'.openpkg'. There are lots of plans on how to use this folder, but until now
the only thing implemented is openpkg-tools' configuration through the file
you mention '.openpkg/build'.
If you want to have the openpkg-tool behave specially (read about -E, -H,
-r from the openpkg-tool manpage) without typing these arguments every time
on the command line, then write a file called 'build' like this:
$ cat build
#-f /home/meuser/.openpkg/00INDEX.rdf
-E pgp2 autoconf
-P sudo
Make a new directory '.openpkg', and put the above file in there with
readable permissions. Now every time you type 'openpkg index' or 'openpkg
build', those arguments will be used.
Regards,
Michael
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe
Cable & Wireless Telecommunications Services GmbH
pgp00000.pgp
Description: PGP signature
