On Mon, 16 Jun 2014, Sune Vuorela wrote:
> > Great -- thanks Sune for the feedback. It is just from previous
> > comments I was not sure if KDE is still relying/using virtuoso.
> > But if you state so -- must be so.
> There is a move away from virtuoso - but the kde stack in stable uses
> virtuoso
> and if users should have a chance to migrate their data out, they need a kde
> stack that can communicate with it.
thank you Sune for further information
> > Do you think it would be feasible to proceed for now with a
> > versioned (e.g. virtuoso-7) source package for virtuoso while excluding
> > all the non-versioned meta- packages, thus providing recent virtuoso for
> > those users who want it, while keeping KDE team and users happy?
> If everytihng is properly versioned, I don't see a issue with providing an
> extra source package, and we could probably even strip down the kde-virtuoso
> source package from a lot of the 'generic components'. It is really just the
> odbc driver
i.e. libvirtodbc0 ? (i.e. versioned only by SOVERSION not virtuoso
version) which depends on virtuoso-opensource-6.1-common ... because of
non-SOVERSION based versioning here (but on internal DRIVER_VERS)
I guess that might be the tricky part. Right?
> and the virtuoso executable that kde relies on.
/usr/bin/virtuoso-t from versioned virtuoso-opensource-6.1-bin
(which seems to not depend on any other virtuoso part, and already
versioned) as called by
./backends/virtuoso/virtuosobackend.cpp: QFileInfo info( dir +
QLatin1String("/virtuoso-t") );
right?
another tricky part here I guess is that kde-runtime only recommends
virtuoso-minimal (and thus two above packages) thus might be tricky to
enforce upgrade happen it would be necessary to ensure a specific
version/versioned-name of it.
> I think patches would be more than welcome.
fair enough.
> > what components of KDE require virtuoso? (only napomuk?) and which
> > tools/libraries in particular?
> It is the nepomuk/soprano chain that requires it. and it is used by the
> activities system, by the file manager (dolphin), the image viewer
> (gwenview),
> the mail stack and probably some I forgotten. But everything is happening
> thru
> nepomuk and soprano.
> oh. and the Debian Krap Team is for packages we don't really love but have to
> care for anyways.
gotcha! ;)
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist, Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
