[gentoo-dev] Ebuild's that new another packages comfigured source

[gentoo-dev] Ebuild's that new another packages comfigured source

[Sean P. Kane]

I am very new to Gentoo development and am trying to create an ebuild
file for linux-wlan-ng. Which among a few other things includes the
drivers for Prism2 based wireless network cards. To compile the PCMCIA
driver it needs to have access to the CONFIGURED pcmcia-cs source code.
Assuming that someone has the USE flag "pcmcia" set how do I tell ebuild
that I need "pcmcia source". If this is impossible should I always
download pcmcia a new, configure and install it and then keep the source
around to do the linux-wlan-ng build from? This seems clumsy and likely
to cause people some grief.

Thoughts beyond this: 

Is there a way to keep the source installed for certain key packages
like pcmcia in a consistent way like the kernel sources are kept around?
Maybe have a USE "KeySourceCode" or something?

Thanks,
Sean
 

Re: [gentoo-dev] Ebuild's that new another packages comfigured source

[Chad M. Huneycutt]

Sean P. Kane wrote:
 > I am very new to Gentoo development and am trying to create an
 > ebuild file for linux-wlan-ng. Which among a few other things
 > includes the drivers for Prism2 based wireless network cards. To
 > compile the PCMCIA driver it needs to have access to the CONFIGURED
 > pcmcia-cs source code. Assuming that someone has the USE flag
 > "pcmcia" set how do I tell ebuild that I need "pcmcia source". If
 > this is impossible should I always download pcmcia a new, configure
 > and install it and then keep the source around to do the
 > linux-wlan-ng build from? This seems clumsy and likely to cause
 > people some grief.

Does the linux-wlan-ng stuff conflict with any other pcmcia-cs modules?
  If not, then just modify the pcmcia-cs ebuild to install the wlan stuff
too.

 >
 > Thoughts beyond this:
 >
 > Is there a way to keep the source installed for certain key packages
 > like pcmcia in a consistent way like the kernel sources are kept
 > around? Maybe have a USE "KeySourceCode" or something?

I see nothing wrong with creating a pcmcia-cs-source ebuild that
copies the configured source to /usr/src after doing the configuration. 
  Well, I guess the only issue would be where to draw the lines about 
which packages have a -source.

Chad

RE: [gentoo-dev] Ebuild's that new another packages comfigured source

[Sean P. Kane]

Chad,

Thanks. I thought about modifying the pcmcia-cs ebuild after posting as
a possible fix. The thing with this is that wlan-ng also builds the PCI
wireless drivers, etc. Maybe I can include it in the PCMCIA ebuild, but
only have it configure the pcmcia driver, and then have a wlan-ng ebuild
that builds everything BUT the PCMCIA driver which should also remove
the need for the PCMCIA source.....

Or create a pcmcia-cd-source ebuild....I'll play with it a bit......

Thanks,
Sean


-----Original Message-----
From: Chad M. Huneycutt [mailto:chad.huneycutt@acm.org] 
Sent: Thursday, April 18, 2002 05:59
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuild's that new another packages comfigured
source


Sean P. Kane wrote:
 > I am very new to Gentoo development and am trying to create an  >
ebuild file for linux-wlan-ng. Which among a few other things  >
includes the drivers for Prism2 based wireless network cards. To  >
compile the PCMCIA driver it needs to have access to the CONFIGURED  >
pcmcia-cs source code. Assuming that someone has the USE flag  >
"pcmcia" set how do I tell ebuild that I need "pcmcia source". If  >
this is impossible should I always download pcmcia a new, configure  >
and install it and then keep the source around to do the  >
linux-wlan-ng build from? This seems clumsy and likely to cause  >
people some grief.

Does the linux-wlan-ng stuff conflict with any other pcmcia-cs modules?
  If not, then just modify the pcmcia-cs ebuild to install the wlan
stuff too.

 >
 > Thoughts beyond this:
 >
 > Is there a way to keep the source installed for certain key packages
> like pcmcia in a consistent way like the kernel sources are kept  >
around? Maybe have a USE "KeySourceCode" or something?

I see nothing wrong with creating a pcmcia-cs-source ebuild that copies
the configured source to /usr/src after doing the configuration. 
  Well, I guess the only issue would be where to draw the lines about 
which packages have a -source.

Chad

_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev