| 1 |
On Sun, 15 Jun 2014 16:06:57 +0700 |
| 2 |
"Vadim A. Misbakh-Soloviov" <mva@×××.name> wrote: |
| 3 |
|
| 4 |
> My idea is to allow failing for some patches without breaking build |
| 5 |
> at all. And, in parallel, to add groupping. |
| 6 |
> |
| 7 |
> [...] |
| 8 |
> |
| 9 |
> Any objections/approvals/suggestions? |
| 10 |
|
| 11 |
What are the use cases of this idea? What is its goal? |
| 12 |
|
| 13 |
In my use case, I've found or written patches with a permanent purpose; |
| 14 |
therefore, I'd like the patches to apply or die hard with a purpose. |
| 15 |
I can't imagine an use case where you don't want them to apply. |
| 16 |
|
| 17 |
Temporary backported patches (eg. from version 2) come to mind; it then |
| 18 |
becomes tricky to know whether it fails because it is the new version |
| 19 |
(2), or whether it is a version (<2) in between that breaks. |
| 20 |
|
| 21 |
That would become a whole new feature request with specific directory, |
| 22 |
file or header syntaxes, which takes time to implement; at which point, |
| 23 |
one wonders if just (re)moving away the patch when you see it fail in |
| 24 |
the early src_prepare phase followed by a --resume is more favorable. |
| 25 |
|
| 26 |
-- |
| 27 |
With kind regards, |
| 28 |
|
| 29 |
Tom Wijsman (TomWij) |
| 30 |
Gentoo Developer |
| 31 |
|
| 32 |
E-mail address : TomWij@g.o |
| 33 |
GPG Public Key : 6D34E57D |
| 34 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives