Speaking about default version of automake... Funny you mention it, a few weeks ago I had a nice discussion with a mdk employee about this topic.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm trying to compile lirc 0.7pre1 to support my PVR-250 and its new remote. However, when running the lirc autogen.sh script it complains that automake v1.5 is required. So: [EMAIL PROTECTED] RPMS]$ rpm -qa|grep automake automake-1.4-23.p6.mdk
Is there a reason that automake1.7 isn't overwriting / upgrading automake-1.4?
Yes, because automake-1.4 is the default version at present, if 1,7 were to overwrite 1.4, no-one would have 1.4 anymore, and 1.7 would be the default (which is not what we want yet apparently).
My issue: automake1.7 as a BuildRequires gets rejected by slbd, because it thinks it's redundant. Rationale:
automake-1.4 Provides: automake
automake1.7 Provides: automake
rpm-build Requires automake.
Since rpm-build (and basesystem) is always required everything that it Requires is redundant. Which makes everything that Provides: automake redundant too. Hence also automake1.7.
Eventually we came to the following conclusion:
- removing "Provides: automake" from automake1.7 (my preference) was not prefered;
- using "automake1.7" to fill in the "Requires automake" in rpmbuild (instead of automake) isn't a good idea, since it pulls in autoconf2.5. This will impact packages that "BuildRequires: autoconf2.5" when building with automake1.4;
- automake-1.4 is not exactly the same as automake1.7 (so perhaps it shouldn't Provide automake after all?). Some packages that work with automake-1.4 may not work with automake1.7, however, we don't know _what_ will be impacted.
anyway... that's the status. we're letting things be as they are for now. I guess automake-1.4 is considered the standard.
regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
