Adeodato Simó a écrit :
* "Adam Cécile (Le_Vert)" [Tue, 03 Jul 2007 08:46:45 +0200]:
Hi Steve,
(My name is not Steve.)
Wasn't talking to new or mistake.
I really hate circular depency and I'm not sure it's the better way.
Well, do as Joss said and tighten the audacious-plugins dependency in
audacious, *and* introduce tight dependencies against audacious in all
the rest of plugin packages. No circular dependencies.
In fact, audacious is broken in testing for ages and forcing a build
of mcs on mipsel would fix all that crap...
Well, sorry but no. It is not broken in testing because of mcs not being
built, it is broken in testing because it's not packaged correctly.
Maybe, I didn't know how to deal with this circular dependency.
Here is what I understand, let me know if there's something wrong:
audacious 1.3.X should depends on audacious-plugins (>= 1.3) and
audacious-plugins (<< 1.4).
That make senses now upstream and me are sure X.Y ABI will always be
incompatible with X.Z ABI.
If it's fine I'll prepare a new upload for it, however I still can't do
anything until mcs is built on mipsel ;)
Cheers,
