1 |
On Sat, Aug 27, 2005 at 06:38:36AM -0500, Brian Harring wrote: |
2 |
> You're masking occurs within the profile itself, not globally. |
3 |
> Global masking usually is for introduction of new ebuilds that need |
4 |
> testing and shouldn't be hit by normal arch testers (portage early |
5 |
> release candidates for example); if you're blocking valgrind on arm |
6 |
> (fex), you *should* be blocking it in profiles/default-linux/arm, not |
7 |
> profiles/package.mask ;) |
8 |
> |
9 |
> If it's profile specified files, relax, not targeted :). |
10 |
> Strictly after getting the global data out of there, and into a |
11 |
> directory reflecting that data's actual role within the repository, |
12 |
> and makes sense in a more flexible, non single |
13 |
> $PORTDIR+$PORTDIR_OVERlAY environment. |
14 |
> |
15 |
> Aside from that, see my other email re: the seperate levels of |
16 |
> filtering :) |
17 |
> ~harring |
18 |
|
19 |
That clarified it for me :) |
20 |
|
21 |
Thanks |
22 |
Ferdy |
23 |
|
24 |
-- |
25 |
\\|// . . . o o o o O O ( Born to be ) |
26 |
o o ( FREE ) |
27 |
+--ooO--O--Ooo-----------------------------------------------+ |
28 |
| Fernando José Pereda GarcimartÃn - http://www.ferdyx.org | |
29 |
| Gentoo Linux Developer - http://dev.gentoo.org/~ferdy | |
30 |
| [ ferdy AT ferdyx DOT org ] && [ ferdy AT gentoo DOT org ] | |
31 |
| 20BB BDC3 761A 4781 E6ED ED0B 0A48 5B0C 60BD 28D4 | |
32 |
+------------------------------------------------------------+ |