Re: [Soprano-devel] Multi-Arch search paths for virtuoso's plugins

[Lisandro Damián Nicanor Pérez Meyer]

On Monday 28 October 2013 09:38:21 Lisandro Damián Nicanor Pérez Meyer wrote:
> On Monday 28 October 2013 10:47:13 Vishesh Handa wrote:
> > Hey everyone
> > 
> > The patch applies perfectly (in the 2.9 branch). However, my cmake foo
> > is not the great, so it would be nice if some else could also take a
> > look at it.
> 
> Great :)
> 
> > @Lisandro: I assume you'll want a new release of Soprano to be made?
> > 2.9.5? Soprano 2.10 is not going to be released, we're going to jump
> > to version 3.0 after this which will break binary compatibility since
> > we will be moving to Qt5.
> 
> Sune Vuorela told me that there might be soprano upstream devs that might be
> using our packaged virtuoso. If we switch virtuoso+soprano to m-a paths,
> their dev builds of soprano will stop working.
> 
> So if the patch gets accepted upstream and you find it ok, we can simply
> patch our current soprano (2.9.3 iirc) and upstream devs will get it the
> necessary changes via soprano's repo.

OK, due to various reasons we need to move forward, so we will apply the 
patch. If you can make a 2.9.5 release, the better :-)

Kinds regards, Lisandro.

-- 

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: [Soprano-devel] Multi-Arch search paths for virtuoso's plugins

[Lisandro Damián Nicanor Pérez Meyer]

On Monday 28 October 2013 10:47:13 Vishesh Handa wrote:
> Hey everyone
> 
> The patch applies perfectly (in the 2.9 branch). However, my cmake foo
> is not the great, so it would be nice if some else could also take a
> look at it.

Great :)
 
> @Lisandro: I assume you'll want a new release of Soprano to be made?
> 2.9.5? Soprano 2.10 is not going to be released, we're going to jump
> to version 3.0 after this which will break binary compatibility since
> we will be moving to Qt5.

Sune Vuorela told me that there might be soprano upstream devs that might be 
using our packaged virtuoso. If we switch virtuoso+soprano to m-a paths, their 
dev builds of soprano will stop working.

So if the patch gets accepted upstream and you find it ok, we can simply patch 
our current soprano (2.9.3 iirc) and upstream devs will get it the necessary 
changes via soprano's repo.


Kinds regards, Lisandro.

-- 
"In college, I cooked some hot dogs by putting metal forks in each end of the
hot dog and running 120 volts through it. Hot dogs have just enough
conductivity so that this works well"
  greenroom(576281) - on a truly geeky way to cook hot dogs.
  Posted in Slashdot, also found in The Open Source Cookbook for Geeks.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: [Soprano-devel] Multi-Arch search paths for virtuoso's plugins

[Vishesh Handa]

Hey everyone

The patch applies perfectly (in the 2.9 branch). However, my cmake foo
is not the great, so it would be nice if some else could also take a
look at it.

@Lisandro: I assume you'll want a new release of Soprano to be made?
2.9.5? Soprano 2.10 is not going to be released, we're going to jump
to version 3.0 after this which will break binary compatibility since
we will be moving to Qt5.


On Sun, Oct 27, 2013 at 3:45 PM, Lisandro Damián Nicanor Pérez
 wrote:
> Hi! I have just filled [0]. This patch detects wheter soprano is being built
> in a Multi-Arch [m-a] aware path using a CMake-provided variable and if so,
> appends the correct search paths.
>
> [0] 
>
> We currently have a FTBFS bug in virtuoso and we would like to add m-a support
> for it in the same upload. This of course will mean that we will also need to
> patch soprano with the provided patch (see bug). So, it would be really cool
> if you can ACK it first.
>
> Kinds regards, Lisandro.
>
> Note: if possible, keep pkg-kde-talk at l.d.o in CC.
>
> --
> A proprietary undocumented text format as the de facto standard -- and that's
> what .doc is -- is a shame for all parties involved. It's like using a special
> patented ink that can only be read with special patented sun glasses. Who
> would want to use that for all their scientific, private and business
> documents? Probably nobody. Why they do so with computers is beyond me.
>   Matthias Ettrich, founder of the KDE project.
>   http://www.efytimes.com/efytimes/25412/news.htm
>
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/
>
> --
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> ___
> Soprano-devel mailing list
> soprano-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/soprano-devel
>



-- 
Vishesh Handa

-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk