[Pkg-xfce-devel] Bug#668806: nmu for xfce4-panel dependencies
- Subject: [Pkg-xfce-devel] Bug#668806: nmu for xfce4-panel dependencies
- From: corsac at debian.org (Yves-Alexis Perez)
- Date: Sun, 22 Apr 2012 14:47:46 +0200
- Message-id: <[🔎] 1335098866.28226.17.camel@scapa>
- In-reply-to: <20120422103332.GJ4238@radis.cristau.org>
- References: <20120414143358.12157.54267.reportbug@scapa> <20120422103332.GJ4238@radis.cristau.org>
On dim., 2012-04-22 at 12:33 +0200, Julien Cristau wrote:
> On Sat, Apr 14, 2012 at 16:33:58 +0200, Yves-Alexis Perez wrote:
> > Xfce 4.10 is around the corner, and like last time, we have some changes
> > in the panel which break the plugins built against the previous (4.8)
> > panel.
> > Like last time, we'd like to push a new 4.8 xfce4-panel with shlibs
> > like:
> > libxfce4panel-1.0 3 xfce4-panel (>= 4.7.7), xfce4-panel (<< 4.9)
> > then make a round of binNMUs for dependencies. So when it's time to
> > upload 4.10, we can safely upload in stable a 4.10 panel with shlibs:
> > libxfce4panel-1.0 4 xfce4-panel (>= 4.9.2)
> > or even
> > libxfce4panel-1.0 4 xfce4-panel (>= 4.9.2), xfce4-panel (<< 4.11)
> > and ask for a second round of binNMUs.
> > Since there are quite some plugins, I didn't yet upload the 4.8.6-4
> > xfce4-panel including the shlibs change, in case you'd like more info on
> > the whole transition. Ping me if/when I can upload.
> So, err, why isn't libxfce4panel a separate package that could change
> names (along with a SONAME bump) when the interface changes?
We thought about this, we even though about this in the 4.6/4.8
transition. Unfortunately, it might not be a good idea, because even if
you split the lib and keep the old lib around when upgrading the panel
and adding a new lib, the plugins built against the old panel might
still not work with the new panel.
> And why
> was the xfce4-panel (<< 4.9) bit not there in the first place if you
> know every release is incompatible?
Well, we don't know that in advance. We could force the conflict by
default and remove it if/when we know that the next panel won't have
issues with old plugins though, but that means ?transition by default?
which you might not like either. If you prefer that default, then I'm ok
to make the switch
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part