On Sat, 07 Jun 2003 01:56:50 +0200 Stefan van der Eijk <[EMAIL PROTECTED]> wrote:
> >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 > OK, sounds fair enough _but_ : DO try to compile enlightenment 17 , have a look at the advanced automake stuff and autogen.sh. Now it's better .. but a year back, compiling this beast on 8.2 / 9.0 / 9.1 was a real pain. Why ? Coz of paths and version checking. Now , if a bright mind renames stuff, that's fine. If another one starts moving stuff arround, fine by me. But if it's not LSB , or if the name of a dep is keeping some source from compiling just because of the name, then I'm against it. And frankly I don't see the advantages of renaming this rpm. Isn't there a way to let urpmi "think" that automake-1.4 == automake1.4 ? And most of all .. will the symlink from automake be to automake-1.4 or automake1.4 . You can imagine that this will cause confusion . My 5 cents .. Cheers -- Thibaut Fernagut, Director of Security Burning Frog - I.T. Services To Set Your World On Fire Doornstraat 32, B-8970, Poperinge, Belgium Tel: +32 (0)57 332967 Fax: +32 (0)57 332967 Mobile: +32 (0)473 774334 Email : [EMAIL PROTECTED] Web: http://www.burningfrog.be
