[gentoo-user] Re: hacking an ebuild
Alan McKinnon alan at linuxholdings.co.za writes: Not sure what you are saying here. Can you give me the explicit line to add to the /etc/portage/package.keywords section-name/package-name * ~* ** Hello Alan, That is a very cool bit of detail you have provided. Most excellent! Now that I have that trick, I have several things to revisit thx James -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: hacking an ebuild
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
What? Why? Just add 'net-analyzer/jffnms ~x86'
On amd64?
Yes.
Well after using alan's suggestion and getting JFFNMS to compile
I just had to try this out. It worked too!
Can you explain why using ~x86 on an amd64 machine works
in the /etc/portage/package.keywords file?
It seem I need to do some more reading
dev-libs/apr-util-0.9.12 fails to compile, so, jffnms cannot compile.
Fails how?
Paraphrased, it said that the Berkeley database was not installed.
Looking at the available packages ('eix berkeley' and then 'eix db')
I figured out that is was because that berkdb is a general system
flag I set in 'make.conf'. So for 'apr-util' in the 'package.use'
file I just removed this flag (-berkdb). I'm not certain what effect
this will have on my system or JFFNMS, if any at all Once this
was fixed using your method or alan's method, JFFNMS compiled.
Now JFFNMS is installed and it's time to configure it and test it.
thanks for all of the help.
James
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: hacking an ebuild
On Friday 22 June 2007 22:42:33 James wrote: What? Why? Just add 'net-analyzer/jffnms ~x86' On amd64? Yes. Well after using alan's suggestion and getting JFFNMS to compile I just had to try this out. It worked too! Can you explain why using ~x86 on an amd64 machine works in the /etc/portage/package.keywords file? It seem I need to do some more reading Because that's the keyword the ebuild has? Why wouldn't it? package.keywords specifies what keywords you are willing to accept for a given package atom... -- Bo Andresen signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: hacking an ebuild
On Thursday 21 June 2007, James wrote: Bo Ørsted Andresen bo.andresen at zlin.dk writes: 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)... Not sure what you are saying here. Can you give me the explicit line to add to the /etc/portage/package.keywords confused section-name/package-name * ~* ** This will make the package visible under just about any circumstance, whether it is stable, unstable or not keyworded for your arch. see 'man 5 portage', section package.keywords around about line 330 for more info. This feature is relatively new and if you last read the howtos some time ago (like me...) you might not be aware of it yet alan -- Optimists say the glass is half full, Pessimists say the glass is half empty, Developers say wtf is the glass twice as big as it needs to be? Alan McKinnon alan at linuxholdings dot co dot za +27 82, double three seven, one nine three five -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: hacking an ebuild
On Thursday 21 June 2007 01:32:39 James wrote: Bo Ørsted Andresen bo.andresen at zlin.dk writes: What? Why? Just add 'net-analyzer/jffnms ~x86' On amd64? Yes. It tried this. It allowed the standard page to be emerge, but it fails to compile dev-libs/apr-util-0.9.12 fails to compile, so, jffnms cannot compile. Fails how? 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)... Not sure what you are saying here. Can you give me the explicit line to add to the /etc/portage/package.keywords I did. -- Bo Andresen signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: hacking an ebuild
On Thursday 21 June 2007 10:01:56 Alan McKinnon wrote: 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)... Not sure what you are saying here. Can you give me the explicit line to add to the /etc/portage/package.keywords confused section-name/package-name * ~* ** * accepts any stable keyword. ~* accepts any testing keyword. -* accepts -* keywords. ** accepts even if there are no keywords at all (which means basically anything will be accepted)... I'd never use ** where it isn't necessary... This will make the package visible under just about any circumstance, whether it is stable, unstable or not keyworded for your arch. It's also redundant (in that ** will cover anything anyway)... ;) see 'man 5 portage', section package.keywords around about line 330 for more info. This feature is relatively new and if you last read the howtos some time ago (like me...) you might not be aware of it yet Only ** was added recently. At the same time KEYWORDS=-* was banned in favour of KEYWORDS=. -- Bo Andresen signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: hacking an ebuild
Alan McKinnon alan at linuxholdings.co.za writes: 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 Ok this sounds like just the sort of advise I was looking for. If I run into trouble I'll post again. Thanks Alan, James -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: hacking an ebuild
Bo Ørsted Andresen bo.andresen at zlin.dk writes: What? Why? Just add 'net-analyzer/jffnms ~x86' On amd64? It tried this. It allowed the standard page to be emerge, but it fails to compile dev-libs/apr-util-0.9.12 fails to compile, so, jffnms cannot compile. 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)... Not sure what you are saying here. Can you give me the explicit line to add to the /etc/portage/package.keywords confused James -- [EMAIL PROTECTED] mailing list
