| 1 |
On 08/09/14 06:47, Rick "Zero_Chaos" Farina wrote: |
| 2 |
> On 09/07/2014 09:03 PM, Rich Freeman wrote: |
| 3 |
>> Right now the general policy is that we don't allow unmasked (hard or |
| 4 |
>> via keywords) ebuilds in the tree if they use an scm to fetch their |
| 5 |
>> sources. There are a bunch of reasons for this, and for the most part |
| 6 |
>> they make sense. |
| 7 |
> Hard masking is a relic from the days that we didn't just have empty |
| 8 |
> keywords, most of the VCS ebuilds in the tree just have empty keywords |
| 9 |
> now and are not actually hard masked. I'd say if you set |
| 10 |
> ACCEPT_KEYWORDS="**" then you get to keep the pieces. |
| 11 |
|
| 12 |
Hard masking is a relic? That's nonsense |
| 13 |
|
| 14 |
It just always has been a decision left for the developer him or herself |
| 15 |
if the masking needs a message or not (package.mask being the way |
| 16 |
to mask package with a message, empty KEYWORDS the |
| 17 |
way you don't need a message) |
Archives