| 1 |
On 2/21/10 10:11 AM, "Paweł Hajdan, Jr." wrote: |
| 2 |
> On 2/21/10 5:08 AM, Ryan Hill wrote: |
| 3 |
>> I have one simple request. When you make a non-trivial change to an ebuild - |
| 4 |
>> a patch, a version bump, anything that can effect the behaviour of the |
| 5 |
>> package - please run the test suite. |
| 6 |
> |
| 7 |
> Yeah, on my dev box I just run with FEATURES="test" all the time. Then |
| 8 |
> it's impossible to forget it. And I also catch failures in other packages. |
| 9 |
|
| 10 |
I just noticed that FEATURES="test" is enabled by default in the |
| 11 |
developer profile, with some other features that make portage more strict. |
| 12 |
|
| 13 |
It also looks like the developer profile is not mentioned in the |
| 14 |
developer docs. |
| 15 |
|
| 16 |
What would you think about better advocating usage of the developer |
| 17 |
profile among developers? Looks like many problems would disappear |
| 18 |
simply because the maintainer of a given package would hit the problem |
| 19 |
first (and fix it before it gets into portage). |
| 20 |
|
| 21 |
Paweł Hajdan jr |
Archives