| 1 |
On Wednesday 20 June 2007 13:29:56 Abraham Marín Pérez wrote: |
| 2 |
> >> Create a user overlay in the usual place - $PORTDIR/local/ |
| 3 |
> >> Copy the ebuild there as normal |
| 4 |
> >> modify KEYWORDS="~x86 ~amd64 |
| 5 |
> >> Check that all the dependencies have amd64 ebuilds as well |
| 6 |
> >> emerge jffnms and see what happens |
| 7 |
> > |
| 8 |
> > What? Why? Just add 'net-analyzer/jffnms ~x86' |
| 9 |
> > to /etc/portage/package.keywords? No matter what the KEYWORDS of an |
| 10 |
> > ebuild are (or aren't) they can be accepted by a proper entry in |
| 11 |
> > package.keywords (** if empty)... |
| 12 |
> |
| 13 |
> I think the problem here is that the package is masked, not marked as |
| 14 |
> unstable; that's the reason to create a new ebuild not affected by the |
| 15 |
> general portage.mask... Am I right? |
| 16 |
|
| 17 |
No. First of all it's not masked. Secondly if it was masked it could be |
| 18 |
unmasked through /etc/portage/package.unmask... |
| 19 |
|
| 20 |
-- |
| 21 |
Bo Andresen |
Archives