On Friday 2016-07-15 15:30, Pekka Paalanen wrote:
>> >OTOH, would adding a new libweston MAJOR in an already stable and
>> >released binary distribution be absolutely forbidden? It would by
>> >definition not affect anything the distribution was released with,
>> >unless libweston's dependencies
On Wed, 13 Jul 2016 16:53:27 +0200 (CEST)
Jan Engelhardt wrote:
> On Wednesday 2016-07-13 13:54, Pekka Paalanen wrote:
> >
> >I think Quentin raised a good point, though. In source-based
> >distros, well, in Gentoo at least which I use almost exclusively,
> >there are no
On Thursday 2016-07-14 17:33, Emil Velikov wrote:
>
>The keypoint here is that one should _not_ need to uninstall
>libdb-4_5-devel in order to have libdb-4_8-devel and vice-versa.
>This is what parallel installability is all about (afaict).
It is indeed what it is about.
But is it _necessary_ to
On 13 July 2016 at 15:53, Jan Engelhardt wrote:
>
> On Wednesday 2016-07-13 13:54, Pekka Paalanen wrote:
>>
>>I think Quentin raised a good point, though. In source-based
>>distros, well, in Gentoo at least which I use almost exclusively,
>>there are no separate -devel packages.
On Wednesday 2016-07-13 13:54, Pekka Paalanen wrote:
>
>I think Quentin raised a good point, though. In source-based
>distros, well, in Gentoo at least which I use almost exclusively,
>there are no separate -devel packages.
A package is, abstractly, merely a selected subset of `make install`
On Sun, 10 Jul 2016 14:34:28 +0200 (CEST)
Jan Engelhardt wrote:
> On Sunday 2016-07-10 13:13, Quentin Glidic wrote:
> >
> > If we install only one .pc file:
> > - You cannot develop against an old version.
>
> I do not feel that is true. If you have Berkeley DB 4.5 in tarball
On Monday 2016-07-11 16:44, Emil Velikov wrote:
>> Without pkgconfig supporting some new alias tag (hint, hint) to cover
>> such a case,
>No idea what such a "alias tag" is supposed to do/look like. Do you
>have examples ?
Proposed concept would be to make pkgconfig recognize
a new Alias
On 11 July 2016 at 17:58, Jan Engelhardt wrote:
>
> On Monday 2016-07-11 16:44, Emil Velikov wrote:
http://ometer.com/parallel.html. I would strongly recommend giving it
a look.
>>>
>>> I read it now, and I do not buy it - at least not for 2016 standards.
>>> According to
On Monday 2016-07-11 16:44, Emil Velikov wrote:
>>>http://ometer.com/parallel.html. I would strongly recommend giving it
>>>a look.
>>
>> I read it now, and I do not buy it - at least not for 2016 standards.
>> According to the page, it was written in 2002, and I can confirm that
>> the situation
On 9 July 2016 at 17:26, Pekka Paalanen wrote:
> On Thu, 7 Jul 2016 17:45:24 +0100
> Emil Velikov wrote:
>
>> On 7 July 2016 at 10:46, Pekka Paalanen wrote:
>> > On Mon, 4 Jul 2016 16:25:54 +0100
>> > Emil Velikov
On 10 July 2016 at 13:23, Jan Engelhardt wrote:
>
> On Sunday 2016-07-10 12:46, Emil Velikov wrote:
>>> PKG_CHECK_EXISTS([gtk-3.0], [PKG_CHECK_MODULES([gtk], [gtk-3.0])], [
>>> ...repeat the fun...
>>> ])]
>>>
>>Yes, it's one line of fun for each version that you want to be
On Sunday 2016-07-10 13:13, Quentin Glidic wrote:
>
> If we install only one .pc file:
> - You cannot develop against an old version.
I do not feel that is true. If you have Berkeley DB 4.5 in tarball
form, you can build and `make install` it. Provided the SONAME is
different (it is;
On Sunday 2016-07-10 12:46, Emil Velikov wrote:
>> PKG_CHECK_EXISTS([gtk-3.0], [PKG_CHECK_MODULES([gtk], [gtk-3.0])], [
>> ...repeat the fun...
>> ])]
>>
>Yes, it's one line of fun for each version that you want to be
>compatible with. It's not ideal, but it's a price to pay, for keeping
>things
On 10/07/2016 12:11, Jan Engelhardt wrote:
On Saturday 2016-07-09 18:24, Pekka Paalanen wrote:
First, what kind of parallel installability is sought?
* just runtime
* parallel development environment (like what e.g. libabw,
librevenge.. do)
everything that is about libweston including
On 10 July 2016 at 11:11, Jan Engelhardt wrote:
>
> On Saturday 2016-07-09 18:24, Pekka Paalanen wrote:
>>>
>>> First, what kind of parallel installability is sought?
>>>
>>> * just runtime
>>> * parallel development environment (like what e.g. libabw,
>>> librevenge.. do)
>>
On Saturday 2016-07-09 18:24, Pekka Paalanen wrote:
>>
>> First, what kind of parallel installability is sought?
>>
>> * just runtime
>> * parallel development environment (like what e.g. libabw,
>> librevenge.. do)
>
>everything that is about libweston including development enviroment
>has
On Sat, 9 Jul 2016 05:19:26 +0200 (CEST)
Jan Engelhardt wrote:
> On Thursday 2016-07-07 11:46, Pekka Paalanen wrote:
> >> >> +AC_SUBST([LIBWESTON_VERSION],
> >> >> [libweston_major_version.libweston_minor_version.libweston_patch_version])
> >> >>
> >> >
> >> > That makes
On Thursday 2016-07-07 11:46, Pekka Paalanen wrote:
>> >> +AC_SUBST([LIBWESTON_VERSION],
>> >> [libweston_major_version.libweston_minor_version.libweston_patch_version])
>> >>
>> >
>> > That makes packaging a pain. Although the whole libweston (supposedly
>> > parallel-installable) is already
On 7 July 2016 at 10:46, Pekka Paalanen wrote:
> On Mon, 4 Jul 2016 16:25:54 +0100
> Emil Velikov wrote:
>
>> On 4 July 2016 at 15:35, Quentin Glidic
>> wrote:
>> > On 04/07/2016 16:23, Emil Velikov wrote:
>> >>
>>
On Mon, 4 Jul 2016 16:25:54 +0100
Emil Velikov wrote:
> On 4 July 2016 at 15:35, Quentin Glidic
> wrote:
> > On 04/07/2016 16:23, Emil Velikov wrote:
> >>
> >> From: Emil Velikov
> >>
> >> Signed-off-by:
On 4 July 2016 at 15:35, Quentin Glidic wrote:
> On 04/07/2016 16:23, Emil Velikov wrote:
>>
>> From: Emil Velikov
>>
>> Signed-off-by: Emil Velikov
>> ---
>> configure.ac | 1 +
>>
From: Emil Velikov
Signed-off-by: Emil Velikov
---
configure.ac | 1 +
libweston/libweston.pc.in | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index be40f10..46b61ae 100644
22 matches
Mail list logo