1 |
> |
2 |
> Related to this... Does anyone know if the PKG_INSTALL_MASK functionality is |
3 |
> broken? It seems to function exactly the same as INSTALL_MASK. The make.conf |
4 |
> man page says PKG_INSTALL_MASK applies only when creating a binary package. |
5 |
> |
6 |
> I'm a relative newbie, but my thinking (consistent with my understanding of the |
7 |
> docs and wisdom gleaned from this list) was to maintain a cross development tree |
8 |
> on my build host with everything installed, including all the build deps |
9 |
> (libraries, header files, etc), while at the same time building binary packages |
10 |
> for what will go onto the target filesystem, using PKG_INSTALL_MASK to filter |
11 |
> out unwanted header files, etc from the binary packages. Then I can create my |
12 |
> lean target filesystem from the binary packages with the |
13 |
> '--root=/target/filesystem' emerge option. But PKG_INSTALL_MASK seems to apply |
14 |
> to my development tree as well. Am I missing anything? |
15 |
|
16 |
|
17 |
Hmm, interesting - that might explain why INSTALL_MASK appears to do |
18 |
nothing at all for me... |
19 |
|
20 |
I suspect (untested) that if you "emerge -k" with FEATURES="buildpkgs" |
21 |
then internally portage is building the package and installing the |
22 |
package? Hence the PKG_INSTALL_MASK will take effect? |
23 |
|
24 |
Just an idea... (off to test it) |
25 |
|
26 |
Ed W |