[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Possible MBF: Packages depending on iceweasel but not firefox/firefox-esr



On 2016-03-20 at 06:43, Jakub Wilk wrote:

> * Josh Triplett <josh@joshtriplett.org>, 2016-03-18, 15:06:

>> Firefox addon packages (xul-ext-*) typically have a Depends on
>> iceweasel, sometimes with alternatives for icedove or other
>> supported packages that can use the addon.  With the switch to
>> firefox and firefox-esr, iceweasel has become a transitional
>> package depending on firefox-esr.  The dependencies of these addon
>> packages prevent installing only the firefox package and removing
>> firefox-esr and the transitional iceweasel package.
> 
> So let's fix Depends of the transitional package. No MBF is needed.

I don't understand how that would help. It would let you install
'firefox-esr | firefox' to satisfy the dependency of xul-ext-foo, but it
would not let you remove iceweasel without also removing xul-ext-foo.


Now, one thing which seems like it _could_ fix this without requiring a
MBF would be for firefox and firefox-esr to acquire 'Provides:
iceweasel'. That seems like a misuse of the system to me, however, and a
suboptimal solution at best.

There is an argument to be made that firefox-esr should Provides:
firefox (or that both should Provides: a single virtual package), or
something along those lines, to avoid requiring packages to list both
alternatives explicitly. I'm not sure that wouldn't have too many
downsides to be a good approach, however.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: