> Hi!
>
> Two (little?) rpm questions.
>
> Is it possible within .spec file to define some rpm variables
> (for example, %requires, maybe %release) based on something
> from running system? Example of usage here is trivial:
No. I tried and it worked, sort of. It got the required value when used to
set environment variables. It did not work internally, and it took me
months to figure what was wrong.
> we can made separate package from pcmcia-cs (currently in kernel)
> and make two packages, e.g. pcmcia-1.3.12...rpm and pcmcia-modules-1.3.12...r
> pm,
> and the last one should require kernel of some exact version
> for that thing was compiled.
For that you need no more than the version it's being built for.
>
> And another one -- is it possible to set some variables in rpm's command line
> ?
> For example, RedHat kernel can be build with lfs patches, but this feature is
> disabled.
> It controlled by "%define lfs 0" in .spec. Can I say, for example,
> "rpm --rebuild kernel-...src.rpm lfn=1" ?
You could do it in ~/.rpmmacros, I think. However, nobody else could build
the same rpm from the same spec file without knowing what peculiar things
you did.
Better to edit the spec file (which you CAN do with a script using ed) and
build source and binary rpms.
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
