On Saturday 23 April 2011 10:19:42 you wrote:
> I see that the {redland,rasqal}-compat packages conflict with
> {redland,rasqal}. In the case of redland-1.0.13-1 and
> redland-compat-1.0.12-1 that means I cannot have both at the same
> time. Which means I have to choose between kdelibs (depends on
> soprano, hence redland-compat) and slv2 (depends on redland-1.0.13)
> (or, in my system, between having KDE software and having ardour).
>
> Any way around this? I'm wondering why redland-compat isn't at the
> same version as redland, though I'm sure if this has been done there's
> a pretty good reason.
Hi,
first of all rasqal > 0.9.21 and redland > 1.0.12, both requires raptor >=
2.0.0 to build, that's because they are out-of-date.
Said that, we cannot ship a redland-base package (for example) and add a
redland-compat package which provides the libraries built with raptor1 and
depends on redland-base.
The only way to install the both version redland and redland-compat is to
rename every file in the redland-compat package, (maybe using --program-suffix/-
prefix) but this will require patches for things like soprano (cmake files and
headers have to point to the -compat stuff). Patches are welcome.
I've no others idea. We've to wait KDE devs port it to raptor2.
--
Andrea
