Dear Adam,
Adam Stirk wrote:
Hmm, what I was thinking of doing was detecting if the madwifi package has been installed
with "pkginstalled madwifi" and from this altering the .config file to include
the madwifi bits. Then I just need a way to get the madwifi source into the hostapd
package so that I keep it generic and could be used by everyone. Is there a way without
adding madwifi to hostapd.desc file?
As, this way it is possible, two and you can use the same
match_source_file to
get the source tarball of the madwifi package, draft skeleton like:
if pkginstalled madwifi; then
file="`match_source_file -p . madwifi`"
# exact and add to configure (or so, etc.)
fi
The arguments to match_source_file are regex to match, by default
of the currently building package, with an additional parameter of the
package specified.
-p to print the whole t2 related download location, otherwise just the
filename as it.
Yours,
Thanks
Adam
-----Original Message-----
From: René Rebe
Sent: 18 August 2008 11:41
To: Adam Stirk
Cc: T2 developers mailing list
Subject: Re: [t2] hostapd
Adam Stirk wrote:
Hi,
I need to build hostapd with madwifi support, this means that I need
access to the madwifi source files when building the hostapd package.
Is there a way that I can do this?
You can add a madwifi source download to the package's .desc file and
unpack it
using hooks during the build. To get the downloaded filename you should use
match_source_file -p
t2-trunk# grep match_source_file package/*/*/*.conf
Yours,
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2
