On 12/20/2004 02:31:44 PM, Tristan Miller wrote:
I'm not so sure about this -- making the internal package name and tarball name different is likely to confuse a lot of users. For example, the package documentation is installed under /usr/share/doc/packages/genpp, which is not what people will be expecting from a program named gpp which comes in an RPM named gpp-2.24-1.rpm and installs a binary named gpp.
The rpm would be named genpp not gpp.
Yes, it's a band aid - the other solution is to file bug reports with the various distributions that have the Obsoletes in their gcc packages.
Also, users will have to use rpm --install gpp* to install the package, but rpm --erase genpp to uninstall it.
No, the spec file would create an rpm called genpp - so they would have to rpm -ih genpp* to install and rpm -e genpp to remove.
Perhaps there's no good solution to this problem except for renaming both the package name and the tarball name to genpp, and possibly also making the install script add a symbol link from /usr/bin/genpp to /usr/bin/gpp to prevent confusion and maintain compatibility with previous versions.
Suggestions?
File a bug report with the distro's for their Obsoletes tag, and hope they agree to remove it. That's the only other solution I can think of.
Well - there is another, but it's a poor one - have the users add the gnu package that has the obsoletes to their yum/apt/up2date/whatever excludes. But then they don't get bug fixes for that, and it is highly dependent upon their distro.
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
