1 |
Hi all, |
2 |
|
3 |
For EAPI 6, introduction of a patch applying function to the package |
4 |
manager itself is being discussed. This would serve two purposes: |
5 |
- support for PATCHES variable in a default src_install phase |
6 |
- a function to apply user patches |
7 |
|
8 |
In bug 463768 the conclusion so far was that implementing the full |
9 |
epatch function in the package manager is not feasible. Therefore, |
10 |
the package manager's implemention would have reduced functionality. |
11 |
The current epatch() would remain available in eutils.eclass for cases |
12 |
where its more advanced modes of operation are needed. |
13 |
|
14 |
The feature list we came up with (see bug 463768 comment 32) includes |
15 |
support for regular patch files, of course. It also includes support |
16 |
for directories, with patches applied in lexical order of their |
17 |
filenames (only files named *.diff and *.patch). |
18 |
|
19 |
So, the questions that I'd like to ask are: |
20 |
1. Is the above set of features reasonable? |
21 |
2. Should the function do automatic -p* detection, or should it |
22 |
default to -p1? Both would be overridable by an explicit -p* |
23 |
option. There are good arguments for either variant (see the |
24 |
above-mentioned bug). |
25 |
3. So far, we don't have a good name for the function. |
26 |
|
27 |
Ulrich |