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

Re: Upstream package splitted into sub-packages: ipe, figtoipe.

On Tuesday 04 December 2007 09:38:09 Nils Philippsen wrote:
> On Tue, 2007-12-04 at 09:27 +0100, Laurent Rineau wrote:
> > Anyway, if I split ipe into two packages, or two sub-packages, how can I
> > provide an upgrade path for users that assume that /usr/bin/figtoipe is
> > provided by ipe, without adding a hard-coded Requires? I am not sure that
> > a solution exists.
> Let both (sub-)packages do this:
> Obsoletes: ipe < 6.0-0.23.pre30
> Conflicts: ipe < 6.0-0.23.pre30

Ok, i see the point.

> I hope your package isn't multilib, in this case current yum in F8 (I
> have yum-3.2.7-1.fc8) would install both architectures even if
> originally only one was installed.

Well... ipe has a ipe-devel sub-packages, to let users create plugins (named 
ipelets). That makes ipe be a multilib package, as far as I know. Is there an 
extra trick to avoid the issue you have spotted?

Laurent Rineau

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