| 1 |
Dnia 2014-02-11, o godz. 19:33:06 |
| 2 |
Chris Reffett <creffett@g.o> napisał(a): |
| 3 |
|
| 4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 5 |
> Hash: SHA1 |
| 6 |
> |
| 7 |
> On 02/11/2014 06:13 PM, Gilles Dartiguelongue wrote: |
| 8 |
> >> Unfortunately, the concurrent nature of gtk2/gtk3 has resulted in |
| 9 |
> >> packages that may support either or both the toolkits. To handle |
| 10 |
> >> this, a few developers have introduced the "gtk3" useflag, that |
| 11 |
> >> prefers gtk3 over gtk2 when both toolkit versions are supported. |
| 12 |
> >> At this point, the Gnome team highly recommends prefering gtk3 if |
| 13 |
> >> possible, skipping the useflag altogether. [1] |
| 14 |
> > |
| 15 |
> > Wrong, as is written in policy whether to prefer gtk2 or 3 is up to |
| 16 |
> > the maintainer of the package. We point people to the fact that |
| 17 |
> > upstream says gtk2 is a dead end and support will stop (if not in |
| 18 |
> > fact already stopped) in the near future. |
| 19 |
> > |
| 20 |
> > We also recommend to have maintainers support slots for their libs |
| 21 |
> > where possible considering man-power and to only choose one toolkit |
| 22 |
> > for applications considering where upstream development is going |
| 23 |
> > and maturity of the port, and again, this is up to package |
| 24 |
> > maintainers. |
| 25 |
> This doesn't make sense to me at all. I can't see why slotted |
| 26 |
> libraries can't just use USE flags to specify what toolkit they're |
| 27 |
> built against, just like any other package in the tree (so, for |
| 28 |
> example, a package that needs webkit-gtk built against gtk3 would |
| 29 |
> depend on webkit-gtk[gtk3] instead of webkit-gtk:3). I'm well aware |
| 30 |
> that there could be limitations I'm unaware of (maybe the package only |
| 31 |
> can build one at a time?), but this is how it looks to me. By |
| 32 |
> switching to versioned gtk flags, this kills two birds with one stone: |
| 33 |
> it makes it obvious to the end user which version they're trying to |
| 34 |
> build their package against, and it gets rid of the need for (ab)using |
| 35 |
> revision numbers to implement slots like that. |
| 36 |
|
| 37 |
Except when you end up rebuilding the huge thing twice. Or trying to |
| 38 |
live with binpackages -- the thing that most Gentoo developers don't |
| 39 |
care about at all. They just love their precious USE flags so much |
| 40 |
they'd shove them everywhere for the sake of it. |
| 41 |
|
| 42 |
-- |
| 43 |
Best regards, |
| 44 |
Michał Górny |
Archives