Re: Precedence for shadowing a monolithic Fedora package?
Using alternatives seems appropriate, but you can also rename the
binary and the .desktop file so you can have a completely parallele
installable version.
Conflicting and Obsoleting fedora maintained packages have be avoided.
2009/8/22 Michel Salim <michael.silvanus(a)gmail.com>:
Hi all,
I maintain sonic-visualiser in Fedora -- it's an audio visualization
tool that can optionally link against libmad, to support manipulating
MP3 files.
The Fedora build, naturally, has this disabled; I made it a build time
switch to quickly enable the feature. It'd be nice if it can be shipped
within RPMfusion, though, but because the package is monolithic, it can
be annoying to do -- one can't just build the full package and then
filter out the core parts, as is done with xine-lib-plugins-freeworld.
What is the recommended way. Use an obsolete? Make them both parallel
installable?
Regards,
--
Michel Salim
<SalimMA(a)fedoraproject.org>
GPG key ID: 78884778
IRC: hircus
Package Sponsor,
Fedora Project