Re: [Cooker] automake-1.4 vs. automake1.7

[Stefan van der Eijk]

Thibaut Fernagut wrote:

[SNIP]

Don't mess with this naming thing pls. automake && autoconf m4 aclocal checking in autogen.sh files to generate configure scripts can fsck a source package really bad.

PLSPLS I urge not to change the naming .

I was just refering to renaming the package, not it's contents.

Does this take any worries away?

Stefan

Not realy,

As for example .. some source packages have actually a README. And sometimes in there , there is a dep-list. Like have automake-1.4

Ah... now we're moving into the consitantly inconsistant linux naming standard area... When you have a bare or old system, then yes, this applies. When you are running a modern distro then what is put into the README's quite often doesn't apply, because many distro's have renamed things already. But mechanisms have been put in place to provide compatibility.

Now , the first thing I always do is urpmi <SELECT_STUFF_FROM_README_> and paste it.

Quite often that'll work, because those generic names are still Provided by the package.

In this case, if automake-1.4 is renamed to automake1.4, it'll still Provide automake.

The rpm-build package will not Require automake, but automake1.4 or automake1.7, which ever is decided to be the standard (scary word) for that release.

I can imagine people having trouble finding the correct name, while now cooker now has allready 1.4 / 1.6 / 1.7

And to be honest .. I don't see why it the rpm itself should be renamed. My logic sence is telling me that a rpm should have the name of the app itself. If one bold user want to compile or rebuild something , s/he will have a hard time after all. Adding this naming to the list is not gonna help.

To the user it really shouldn't matter what the package is called, as long as it is installed when it needs to be. Wether we call automake-1.4 automake1.4 or something else, as long as it Provides automake (like automake1.6 and automake1.7 do) then there isn't an issue. In the end the user will probably be installing rpm-build (which pulls in the compiler, autoconf, automake and loads of other stuff that you _need_ to build a package). Once rpm-build is on a system all those BuildRequires for automake (not automake1.4, automake1.7 --> those are version specific) are redundant.

regards,

Stefan

smime.p7s
Description: S/MIME Cryptographic Signature