1 |
W dniu pią, 16.03.2018 o godzinie 08∶11 +0000, użytkownik Joakim |
2 |
Tjernlund napisał: |
3 |
> On Thu, 2018-03-15 at 20:22 +0100, Michał Górny wrote: |
4 |
> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. |
5 |
> > |
6 |
> > |
7 |
> > Hi, |
8 |
> > |
9 |
> > Here are three of four INSTALL_MASK updates I've sent long time ago |
10 |
> > which were not really reviewed. The fourth patch added support |
11 |
> > for repo-defined install-mask.conf and I'll do that separately. |
12 |
> > |
13 |
> > Those patches focus on smaller changes. What they change, in order: |
14 |
> > |
15 |
> > 1. Removes explicit file removal code for FEATURES=no*. Instead, those |
16 |
> > values are converted into additional INSTALL_MASK entries |
17 |
> > and handled directly via INSTALL_MASK processing. |
18 |
> > |
19 |
> > 2. Rework INSTALL_MASK to filter files while installing instead of |
20 |
> > pre-stripping them. In other words, before: INSTALL_MASK removes |
21 |
> > files from ${D} before merge. After: ${D} contains all the files, |
22 |
> > Portage just skip INSTALL_MASK-ed stuff, verbosely indicating that. |
23 |
> |
24 |
> Will this also remove corresponding split debug files? |
25 |
> There would be little/no point in keeping debug syms if the binary has been |
26 |
> MASKed |
27 |
> |
28 |
|
29 |
Nope. Add both paths to INSTALL_MASK. Expecting it to do implicit magic |
30 |
is a very bad idea. |
31 |
|
32 |
-- |
33 |
Best regards, |
34 |
Michał Górny |