| 1 |
On Sun, Nov 21, 2010 at 01:11:53PM +0000, Markos Chandras wrote: |
| 2 |
> Hi there, |
| 3 |
> |
| 4 |
> The official policy for live ebuilds is the following one: |
| 5 |
> |
| 6 |
> http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/cvs-sources/index.html |
| 7 |
> |
| 8 |
> I don't quite agree with this policy and I guess most of you don't agree |
| 9 |
> either looking at the number of live ebuilds/package.mask entries. |
| 10 |
> |
| 11 |
> My proposal is to keep empty keywords on live ebuilds without masking |
| 12 |
> them via package.mask |
| 13 |
> |
| 14 |
> Users interpret this as a 'double masking' which in fact it is since |
| 15 |
> they need to touch two files before they are able to use the package. |
| 16 |
|
| 17 |
I agree. Forcing the users to add ${P} ** in their keywords is enough, |
| 18 |
it states that "they're on their own". |
| 19 |
|
| 20 |
> I also know that we can use overlays for that, but distribute the |
| 21 |
> ebuilds among dev/proj overlays is not always a solution. |
| 22 |
|
| 23 |
+1 |
| 24 |
|
| 25 |
for big projects like KDE, overlays are a better place, but for small |
| 26 |
packages, they are overkill. |
| 27 |
|
| 28 |
-- |
| 29 |
Alex Alexander | wired |
| 30 |
+ Gentoo Linux Developer |
| 31 |
++ www.linuxized.com |
Archives