| 1 |
>>>>> On Wed, 21 Sep 2016, Kent Fredric wrote: |
| 2 |
|
| 3 |
>> Under that new scheme, how would I apply patches unpacked into |
| 4 |
>> WORKDIR? In EAPI 6, I can put them into the PATCHES variable and use |
| 5 |
>> the default src_prepare to process it. |
| 6 |
|
| 7 |
> oh. Right. Huh, I had somehow overlooked there was already a PATCHES |
| 8 |
> in EAPI6, because I'd been using an equivalent since EAPI5 :) |
| 9 |
|
| 10 |
> Right, so this would kill 90% of my suggestion by |
| 11 |
> already-being-defined. |
| 12 |
|
| 13 |
> So the only remaining thing to think about in terms of usefulness is |
| 14 |
> the ability for repoman to potentially validate entries in PATCHES. |
| 15 |
|
| 16 |
> In your scenario where you have local patches instead of patches in |
| 17 |
> ${FILESDIR}, what does the contents of PATCHES look like? |
| 18 |
|
| 19 |
Well, it could contain entries for both types of paths, like |
| 20 |
"${WORKDIR}"/path/to/foo.patch or "${FILESDIR}"/path/to/bar.patch. |
| 21 |
|
| 22 |
> Would there be a way to identify entries in PATCHES that are |
| 23 |
> children of ${FILESDIR} during `repoman full` and assert they exist? |
| 24 |
|
| 25 |
Obviously they could be identified by their explicit ${FILESDIR}. |
| 26 |
|
| 27 |
Ulrich |
Archives