2014-06-12 13:58 GMT+02:00 Jaromír Mikeš :
> 2014-01-30 8:33 GMT+01:00 Alessio Treglia :
>
> On Mon, Jan 27, 2014 at 12:50 PM, Jonas Smedegaard wrote:
>> > Here's my suggestion:
>>
>> > How does that sound?
>>
>> Cool, +1.
>> I can start implementing such a good idea.
>>
>
> Any progress here?
>
2014-01-30 8:33 GMT+01:00 Alessio Treglia :
> On Mon, Jan 27, 2014 at 12:50 PM, Jonas Smedegaard wrote:
> > Here's my suggestion:
>
> > How does that sound?
>
> Cool, +1.
> I can start implementing such a good idea.
>
Any progress here?
There are few problems related to this (drumkv1,samplv1,syn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/2014 09:55 PM, Jaromír Mikeš wrote:
> 2014-01-26 Reinhard Tartler
>
>> In order for this to work, everything that loads lv2 plugins must
>> be able to lookup the plugins from the updated paths, though!
>
>
> Yes, thats a catch. I am afraid
On Thu, Jan 30, 2014 at 9:47 AM, Felipe Sateler wrote:
> On Thu, Jan 30, 2014 at 6:40 AM, Alessio Treglia wrote:
>> On Mon, Jan 27, 2014 at 12:50 PM, Jonas Smedegaard wrote:
>>> 2) Introduce new package lv2-legacy-support
>>> * Upload only to experimental for now
>>> * Contains symlink
On Thu, Jan 30, 2014 at 6:40 AM, Alessio Treglia wrote:
> On Mon, Jan 27, 2014 at 12:50 PM, Jonas Smedegaard wrote:
>> 2) Introduce new package lv2-legacy-support
>> * Upload only to experimental for now
>> * Contains symlink /usr/lib/$ARCH/lv2/ → /usr/lib/lv2/
>> * Breaks versioned
On Mon, Jan 27, 2014 at 12:50 PM, Jonas Smedegaard wrote:
> 2) Introduce new package lv2-legacy-support
> * Upload only to experimental for now
> * Contains symlink /usr/lib/$ARCH/lv2/ → /usr/lib/lv2/
> * Breaks versioned against all current LV2 plugins
Just a small addition: that wo
On Mon, Jan 27, 2014 at 12:50 PM, Jonas Smedegaard wrote:
> Here's my suggestion:
> How does that sound?
Cool, +1.
I can start implementing such a good idea.
--
Alessio Treglia | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer| quadris...
2014-01-30 Reinhard Tartler
> On Wed, Jan 29, 2014 at 5:57 PM, Jaromír Mikeš
> wrote:
>
> >
> https://wiki.debian.org/Multiarch/TheCaseForMultiarch#A32.2F64_Architectures
> > Did I misunderstand this?
>
> The "Current practices" section explains pretty clearly what
> RedHat/Fedora implement *ins
2014-01-29 Reinhard Tartler
> On Wed, Jan 29, 2014 at 5:44 PM, Jaromír Mikeš
> wrote:
>
> > Multiarch is nowadays widespread in many other distributions:
> > debian and derivatives, redhat and derivatives, opensuse, arch linux
> > and probably others (just quick research correct me if I am wrong
2014-01-27 Jonas Smedegaard
> Quoting Alessio Treglia (2014-01-27 13:22:27)
>
Hi Jonas,
> > On Mon, Jan 27, 2014 at 11:21 AM, Jaromír Mikeš
> wrote:
> > > /usr/lib64 shouldn't be used on debian ...
> > > After some discussion with him he send me a patch ...
> > > Now all *.so files are instal
Quoting Jaromír Mikeš (2014-01-27 12:21:43)
> 1) When updating synthv1 samplv1 drumkv1 LV2 plugins I realize that
> upstream using paths like this:
> /usr/lib/lv2/synthv1.lv2/synthv1.so
> /usr/lib64/lv2/synthv1.lv2/synthv1_ui.so
>
> /usr/lib64 shouldn't be used on debian ...
> After some discussio
Quoting Alessio Treglia (2014-01-27 13:22:27)
> On Mon, Jan 27, 2014 at 11:21 AM, Jaromír Mikeš wrote:
> > /usr/lib64 shouldn't be used on debian ...
> > After some discussion with him he send me a patch ...
> > Now all *.so files are installed this way:
> > /usr/lib/x86_64-linux-gnu/lv2/synthv1.l
2014-01-27 Alessio Treglia
> On Mon, Jan 27, 2014 at 11:21 AM, Jaromír Mikeš
> wrote:
> > /usr/lib64 shouldn't be used on debian ...
> > After some discussion with him he send me a patch ...
> > Now all *.so files are installed this way:
> > /usr/lib/x86_64-linux-gnu/lv2/synthv1.lv2/synthv1.so
>
On Mon, Jan 27, 2014 at 11:21 AM, Jaromír Mikeš wrote:
> /usr/lib64 shouldn't be used on debian ...
> After some discussion with him he send me a patch ...
> Now all *.so files are installed this way:
> /usr/lib/x86_64-linux-gnu/lv2/synthv1.lv2/synthv1.so
> /usr/lib/x86_64-linux-gnu/lv2/synthv1.lv
2014-01-27 Alessio Treglia
> Hi all,
>
> On Sun, Jan 26, 2014 at 8:55 PM, Jaromír Mikeš
> wrote:
> > Alessio, Adrian can you comment pls?
>
> I never managed to solve it once and for all mostly because it seems
> upstream is not taking it as an important issue.
> The thing is: we can do it but I
Hi all,
On Sun, Jan 26, 2014 at 8:55 PM, Jaromír Mikeš wrote:
> Alessio, Adrian can you comment pls?
I never managed to solve it once and for all mostly because it seems
upstream is not taking it as an important issue.
The thing is: we can do it but I'm not sure most client applications
are read
2014-01-26 Reinhard Tartler
> On Sat, Jan 25, 2014 at 7:49 PM, Jaromír Mikeš
> wrote:
> > Hi there,
> >
> > I need some clarification about lv2-plugins install path.
> > LV2 plugins are installed in in path like this:
> > /usr/lib/lv2/drumkv1.lv2/drumkv1.
On Sat, Jan 25, 2014 at 7:49 PM, Jaromír Mikeš wrote:
> Hi there,
>
> I need some clarification about lv2-plugins install path.
> LV2 plugins are installed in in path like this:
> /usr/lib/lv2/drumkv1.lv2/drumkv1.so
>
> But why not in multi-arch path like this rather?
> /
Hi there,
I need some clarification about lv2-plugins install path.
LV2 plugins are installed in in path like this:
/usr/lib/lv2/drumkv1.lv2/drumkv1.so
But why not in multi-arch path like this rather?
/usr/lib/x86_64-linux-gnu/lv2/drumkv1.lv2/drumkv1.so
regards
mira
19 matches
Mail list logo
