On Fri, Jul 28, 2023 at 03:16:53PM +0000, Klemens Nanni wrote: > On Fri, Jul 28, 2023 at 12:18:16PM +0000, Klemens Nanni wrote: > > On Tue, Jul 25, 2023 at 05:06:35PM +0000, Klemens Nanni wrote: > > > On Tue, Jul 25, 2023 at 04:42:10PM +0000, Klemens Nanni wrote: > > > > After one of the recent www/iridum updates, the extension/native host > > > > now > > > > works there just like it does with www/chromium. > > > > > > > > Is this the right way to depend on either chromium or iridium? > > > > The way I understand this: use either iridium-* or chromium-* if > > > > installed, > > > > otherwise install www/chromium to satisfy the runtime dependency. > > espie explained to me that this is how it is intended to work, but... > > > > > > Not in practise, as I can't uninstall chromium when iridium is > > > installed: > > we have no code yet for these uninstall/replace paths, so using variant > dependencies, does not seem useful to me until these bits are implemented.
To be fair, most alternates dependencies do conflict, and the bits involved work just fine with pkg_add -r. The *idea* of differing runtime dependencies is actually fairly rare.
