Bo Ørsted Andresen escribió:
On Tuesday 19 June 2007 14:32:15 Alan McKinnon wrote:
I took a quick look inside the ebuils. Nothing there seems amd64
specific, so here's how I would proceed;
Create a user overlay in the usual place - $PORTDIR/local/
Copy the ebuild there as normal
modify KEYWORDS="~x86 ~amd64
Check that all the dependencies have amd64 ebuilds as well
emerge jffnms and see what happens
What? Why? Just add 'net-analyzer/jffnms ~x86'
to /etc/portage/package.keywords? No matter what the KEYWORDS of an ebuild
are (or aren't) they can be accepted by a proper entry in package.keywords
(** if empty)...
I think the problem here is that the package is masked, not marked as
unstable; that's the reason to create a new ebuild not affected by the
general portage.mask... Am I right?
--
--
[EMAIL PROTECTED] mailing list
