| 1 |
Rémi Cardona wrote: |
| 2 |
> Could you list the packages which could use this? Because if only 3 pkgs |
| 3 |
> need it, it might not be worth the hassle to add it. |
| 4 |
/usr/portage $ grep -lR 'GAMES_CHECK_LICENSE="yes"' *games*|wc -l |
| 5 |
40 |
| 6 |
|
| 7 |
I'm ofc not including fetch-restricted which also require interaction, |
| 8 |
although that is standardised enough for a script to deal with[1]. Having |
| 9 |
found this for games, I can deal with that too ofc, but I still think the |
| 10 |
idea has merit. Consider, for example, a package with separate licenses for |
| 11 |
parts, some of which the user may be happy with, others not. ATM the only |
| 12 |
way to do that is with split ebuilds, aiui. |
| 13 |
|
| 14 |
> As you pointed it out, ebuilds should not be interactive. Imho, adding |
| 15 |
> an eclass to encourage it is counter-productive. |
| 16 |
> |
| 17 |
Wow a humble gentoo dev! /me gets up off floor ;) |
| 18 |
|
| 19 |
I understand that games are a `special case', but why not make it a |
| 20 |
RESTRICT=interact which would automatically mean repoman would not allow |
| 21 |
the package into stable, and admins could easily weed such packages out? |
| 22 |
That way any category could use the same thing for packages with more |
| 23 |
restrictive licenses. (I'm not suggesting this should be merged with |
| 24 |
fetch-restricted as I accept that some stable Java packages have this set, |
| 25 |
and there's zero benefit in changing them.) |
| 26 |
|
| 27 |
So yeah I guess it's encouragement, but if the policy is such packages can |
| 28 |
never hit stable, where's the harm? A user has to explicitly allow such a |
| 29 |
package (or run unstable in which case they will be used to dealing with |
| 30 |
glitches ;) and scripts can still avoid interactive packages. (And bear in |
| 31 |
mind, it's not just uis we're talking about, but stuff like QA automation.) |
| 32 |
|
| 33 |
My 2p. |
| 34 |
|
| 35 |
[Apologies to older devs if this is a rehashed discussion.. Ignore Thread in |
| 36 |
Kontact is fantastic ;p Besides, circumstances _change_. All it comes down |
| 37 |
it to is: A) how useful is it? and B) how tough is it to implement? The |
| 38 |
rest of it's horsesh1t imnsho. C) who will implement? is usually whichever |
| 39 |
idiot came up with it ;) (see the original thread for an example of how |
| 40 |
this list /could/ *work*.)] |
| 41 |
|
| 42 |
[1] http://forums.gentoo.org/viewtopic-t-546828.html There'll be a new one |
| 43 |
out in a few days with a really nice --sync interface; and no hanging on |
| 44 |
game installs :D |
| 45 |
|
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives