| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 25/02/14 11:16 AM, Samuli Suominen wrote: |
| 5 |
> |
| 6 |
> On 25/02/14 18:12, Rich Freeman wrote: |
| 7 |
>> On Tue, Feb 25, 2014 at 10:27 AM, Mart Raudsepp <leio@g.o> |
| 8 |
>> wrote: |
| 9 |
>>> We acknowledge that our policy may not have been perfect but we |
| 10 |
>>> need time to analyze claims brought up by/to the QA team to |
| 11 |
>>> construct a proper proposal for a better policy that would |
| 12 |
>>> satisfy everyone; hopefully in co-operation with a QA team. |
| 13 |
>> Is there any reason to think that this analysis will come to a |
| 14 |
>> different conclusion? |
| 15 |
>> |
| 16 |
>> I don't see any concerns on the list that weren't addressed |
| 17 |
>> already. USE=gtk2 means build gtk2 support USE=gtk3 means build |
| 18 |
>> gtk3 support USE="gtk2 gtk3" means build support for whichever |
| 19 |
>> version the maintainer thinks is better (which is what USE=gtk |
| 20 |
>> meant a week ago) |
| 21 |
> |
| 22 |
> And how does one select 'the best supported GTK+ for this |
| 23 |
> application, selected by the package's maintainer.' ? I want latest |
| 24 |
> best supported GTK+ enabled for all of my packages. I can't figure |
| 25 |
> out the USE combination from those. You can't surely assume every |
| 26 |
> user to review every single package and decide for himself after |
| 27 |
> reading hours, days, weeks, if not even months various package |
| 28 |
> ChangeLogs, NEWS files, and other possible ways upstreams are |
| 29 |
> communicating with? And how does user know of all the mail that |
| 30 |
> goes between upstream and package maintainers about what to choose |
| 31 |
> for distribution? |
| 32 |
|
| 33 |
|
| 34 |
...? as per above, USE="gtk2 gtk3", in make.conf. No need to read |
| 35 |
anything or track changelogs or anything else. Enable both in the |
| 36 |
profile (I'm guessing they'll both probably be enabled by default in |
| 37 |
the desktop profile or a sub-profile, tbh) and you're done. |
| 38 |
|
| 39 |
If you (as a user) want to experiment with the one the maintainer |
| 40 |
DIDN'T choose, then set a single specific version for that atom in |
| 41 |
package.use |
| 42 |
|
| 43 |
|
| 44 |
-----BEGIN PGP SIGNATURE----- |
| 45 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 46 |
|
| 47 |
iF4EAREIAAYFAlMMxbYACgkQ2ugaI38ACPDzGgD/VT5trwwNgxgx6Dc1tbOHiFU+ |
| 48 |
3SBbtcOcxZuTKemK+PIBAJ+uJNWpOzMh+HQV166/QWribofssZF4VTdVZfd+ncMt |
| 49 |
=qBcA |
| 50 |
-----END PGP SIGNATURE----- |
Archives