| 1 |
We're actually using portage 2.1-r2 and INSTALL_MASK does exactly what |
| 2 |
we need it to do for binary packages. |
| 3 |
|
| 4 |
We're building binary packages from source and then install them into |
| 5 |
the target using something like this: |
| 6 |
|
| 7 |
INSTALL_MASK="$(cat "${CONFIG_DIR}/install-mask.txt")" ROOT="$ |
| 8 |
{ROOTFS}" emerge -Kv ${EBUILDS} |
| 9 |
|
| 10 |
and it works just fine. "install-mask.txt" would contain everything |
| 11 |
that we don't want in the target (quite some list), one item per line |
| 12 |
such as: |
| 13 |
> *.h |
| 14 |
> *.hh |
| 15 |
> *.c |
| 16 |
> *.in |
| 17 |
> *.cpp |
| 18 |
> *.C |
| 19 |
> *.la |
| 20 |
> *.a |
| 21 |
> *README* |
| 22 |
etc. |
| 23 |
|
| 24 |
Also |
| 25 |
|
| 26 |
INSTALL_MASK="$(cat "${CONFIG_DIR}/install-mask.txt")" ROOT="$ |
| 27 |
{ROOTFS}" emerge --info |
| 28 |
|
| 29 |
displays INSTALL_MASK correctly. |
| 30 |
|
| 31 |
I think I also tried the same concept with later versions of portage |
| 32 |
and never had a problem (except when I had "*portage*" in my |
| 33 |
INSTALL_MASK, because emerge uses /var/tmp/portage internally and this |
| 34 |
seems to be affected by INSTALL_MASK, too). |
| 35 |
|
| 36 |
Dirk |
| 37 |
|
| 38 |
> Hi everyone, |
| 39 |
> |
| 40 |
> I'm in the process of installing a bunch of packages to make an EEE |
| 41 |
> pc root filesystem right now, and I've noticed that INSTALL_MASK is |
| 42 |
> not masking out the *.h files that I don't need. |
| 43 |
> |
| 44 |
> After doing a bit of looking, I found this gentoo bug that seems to |
| 45 |
> be from portage-2.1_pre6 |
| 46 |
> |
| 47 |
> http://bugs.gentoo.org/show_bug.cgi?id=81025 |
| 48 |
> |
| 49 |
> I'm using portage-2.1.4.4 and I can only guess that INSTALL_MASK is |
| 50 |
> still not implemented for installing from binary packages. |
| 51 |
> |
| 52 |
> Does anyone know if that is correct? |
| 53 |
> |
| 54 |
> Cheers, |
| 55 |
> |
| 56 |
> Chris |
| 57 |
> -- |
| 58 |
> gentoo-embedded@l.g.o mailing list |
| 59 |
> |
Archives