hacking an ebuild

Hello,


The devs seems to be busy. Also, I should have learn this
some time
ago anyway. There is a existing ebuild for JFFNMS, but, it
is masked
for amd64. Is there a guide I can follow to use an x86
ebuild and
create an amd64 derivative ebuild? Since it uses php and
other high
level software, I would not think that this is a terrible
difficult
process....?

If not, can somebody briefly itemized what needs to be
done,
in very general terms, to hack together an ebuild for amd64
when one exist for x86?


James



-- 
gentoo-usergentoo.org mailing list

I advise you to read the dev howto at
http://www.gentoo.org/doc/en/index.xml?catid=gentoodev


Gal'

2007/6/19, James <wirelesstampabay.rr.com>:
> Hello,
>
>
> The devs seems to be busy. Also, I should have learn
this some time
> ago anyway. There is a existing ebuild for JFFNMS, but,
it is masked
> for amd64. Is there a guide I can follow to use an x86
ebuild and
> create an amd64 derivative ebuild? Since it uses php
and other high
> level software, I would not think that this is a
terrible difficult
> process....?
>
> If not, can somebody briefly itemized what needs to be
done,
> in very general terms, to hack together an ebuild for
amd64
> when one exist for x86?
>
>
> James
>
>
>
> --
> gentoo-usergentoo.org mailing list
>
>
-- 
gentoo-usergentoo.org mailing list

On Tuesday 19 June 2007, James wrote:
> Hello,
>
>
> The devs seems to be busy. Also, I should have learn
this some time
> ago anyway. There is a existing ebuild for JFFNMS, but,
it is masked
> for amd64. Is there a guide I can follow to use an x86
ebuild and
> create an amd64 derivative ebuild? Since it uses php
and other high
> level software, I would not think that this is a
terrible difficult
> process....?
>
> If not, can somebody briefly itemized what needs to be
done,
> in very general terms, to hack together an ebuild for
amd64
> when one exist for x86?

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

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
-- 
gentoo-usergentoo.org mailing list

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)...

-- 
Bo Andresen

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?

-- 
-- 
gentoo-usergentoo.org mailing list

On Wednesday 20 June 2007 13:29:56 Abraham Marín Pérez
wrote:
> >> 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?

No. First of all it's not masked. Secondly if it was masked
it could be 
unmasked through /etc/portage/package.unmask...

-- 
Bo Andresen

On Wednesday 20 June 2007, Bo Ørsted Andresen wrote:
> 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)...

<sigh>

Yes, you are right. What was I thinking? It must have been
late at the 
time.

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
--
gentoo-usergentoo.org mailing list

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
--
GENTOO-USERGENTOO.ORG MAILING LIST

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

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