On 00:13 Wed 12 Feb , Gilles Dartiguelongue wrote:
> Right now, I don't really get the point of this discussion given all the
> precedent threads about this, be it 2 years ago and 8-10 years ago.
I spent a while tonight digging up this post from 2005, which nicely
describes where we were with
18.02.2014 13:39, Ben de Groot пишет:
> On 12 February 2014 07:04, Samuli Suominen wrote:
> [...]
>>
>> It's sad that people don't follow common sense (which happens to be the
>> GNOME highlights)
>> and that everything must be turned into a policy of somesort so people
>> get it.
>>
> [...]
>>
>>
On 12 February 2014 07:04, Samuli Suominen wrote:
[...]
>
> It's sad that people don't follow common sense (which happens to be the
> GNOME highlights)
> and that everything must be turned into a policy of somesort so people
> get it.
>
[...]
>
> Just make the gnome gtk3 policy the guideline if yo
On Wed, Feb 12, 2014 at 2:46 PM, Chris Reffett wrote:
> On 2/12/2014 3:09 AM, Michał Górny wrote:
>> Dnia 2014-02-11, o godz. 19:33:06 Chris Reffett
>> napisał(a):
>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>>
>>> On 02/11/2014 06:13 PM, Gilles Dartiguelongue wrote:
> Unfortunately
Le mercredi 12 février 2014 à 17:46 -0500, Chris Reffett a écrit :
> splits it into two
> separate packages, and I suspect that the times where you will have to
> rebuild are when a package needs webkit-gtk to support another toolkit
> (which should happen only once), and when you upgrade (in which
On 2/12/2014 3:09 AM, Michał Górny wrote:
> Dnia 2014-02-11, o godz. 19:33:06 Chris Reffett
> napisał(a):
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 02/11/2014 06:13 PM, Gilles Dartiguelongue wrote:
Unfortunately, the concurrent nature of gtk2/gtk3 has
resulted in pa
On Wed, 12 Feb 2014 09:05:59 +0100
Michał Górny wrote:
> Dnia 2014-02-12, o godz. 00:39:14
> Alex Alexander napisał(a):
>
> > Some developers choose to follow the Gnome team's highlights, while
> > others choose to go their own way. The QA team would like to
> > establish a guideline that solve
Le mercredi 12 février 2014 à 08:29 +0100, Lars Wendler a écrit :
[...]
>
> This is a really good idea and I am all in favor of it.
> gtk+:3 still isn't adopted widely and there are still not many good
> looking skins available for it. (sorry but I don't want to have all gtk+
> apps I am using loo
Le mardi 11 février 2014 à 19:33 -0500, Chris Reffett a écrit :
> This doesn't make sense to me at all. I can't see why slotted
> libraries can't just use USE flags to specify what toolkit they're
> built against, just like any other package in the tree (so, for
> example, a package that needs webk
Dnia 2014-02-11, o godz. 19:33:06
Chris Reffett napisał(a):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/11/2014 06:13 PM, Gilles Dartiguelongue wrote:
> >> Unfortunately, the concurrent nature of gtk2/gtk3 has resulted in
> >> packages that may support either or both the toolkits
Dnia 2014-02-12, o godz. 00:39:14
Alex Alexander napisał(a):
> Some developers choose to follow the Gnome team's highlights, while others
> choose to go their own way. The QA team would like to establish a guideline
> that solves this problem in the best way possible.
First of all, I think that
Hi,
On Wed, 12 Feb 2014 00:39:14 +0200 Alex Alexander wrote:
>Hello fellow developers,
>
>In the first meeting of the new QA team, we discussed the state of the
>gtk{,2,3} USE flags in the main tree. [0]
>
>In its current state, USE="gtk" means gtk2. The Gnome team is trying
>to change this into
El mar, 11-02-2014 a las 19:33 -0500, Chris Reffett escribió:
[...]
> This doesn't make sense to me at all. I can't see why slotted
> libraries can't just use USE flags to specify what toolkit they're
> built against, just like any other package in the tree (so, for
> example, a package that needs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2014 06:13 PM, Gilles Dartiguelongue wrote:
> Thanks for attaching link to team's policy which tries to lift any
> kind of ambiguities people may have for what concerns gnome team's
> packages, I hope it proved useful in your discussions.
>
>
> On Wed, 12 Feb 2014, Samuli Suominen wrote:
> But applications is whole different story...
> The maintainer makes the decision which toolkit is used and best
> supported. If some application has initial port to gtk3, but still
> lacks some features the gtk2 version still had, then maintaine
On 12/02/14 01:51, Ulrich Mueller wrote:
>> On Wed, 12 Feb 2014, Samuli Suominen wrote:
>> USE="gtk3" is valid only for libraries when it's not easy to
>> split/slot as a temporary flag. Applications should simply pick one,
>> the latest one that works, since anything else is obviously
>> redu
> On Wed, 12 Feb 2014, Samuli Suominen wrote:
> USE="gtk3" is valid only for libraries when it's not easy to
> split/slot as a temporary flag. Applications should simply pick one,
> the latest one that works, since anything else is obviously
> redudant.
I don't see why applications should be
Thanks for attaching link to team's policy which tries to lift any kind
of ambiguities people may have for what concerns gnome team's packages,
I hope it proved useful in your discussions.
Le mercredi 12 février 2014 à 00:39 +0200, Alex Alexander a écrit :
> Hello fellow developers,
>
> In the f
On 12/02/14 00:39, Alex Alexander wrote:
> Hello fellow developers,
>
> In the first meeting of the new QA team, we discussed the state of the
> gtk{,2,3} USE flags in the main tree. [0]
>
> In its current state, USE="gtk" means gtk2. The Gnome team is trying to change
> this into "the most recent
Hello fellow developers,
In the first meeting of the new QA team, we discussed the state of the
gtk{,2,3} USE flags in the main tree. [0]
In its current state, USE="gtk" means gtk2. The Gnome team is trying to change
this into "the most recent gtk version" (it is a work in progress).
Unfortunate
20 matches
Mail list logo
