madwifi-ng-dev_0.9.0+svn1416-1
Kel Modderman
kelrin at tpg.com.au
Sun Feb 5 04:56:49 UTC 2006
Pascal DORMEAU wrote:
> Hi,
>
> Why is madwifi-ng-dev depending on madwifi-ng-source ?
My reasoning for it so far is; the includes installed by madwifi-dev can
only be used with the matching source version of the module (or with
more recent snapshots when these includes remain unchanged).
>
> In the madwifi-ng-dev package description, for the example given
> (compiling wpa_supplicant), the source tree is not necessary, the
> includes are enough (from my experience with wpa_supplicant
> compilation). Moreover, when the source package is installed, the
> source tree is not untared (still inside /usr/src/madwifi-ng.tar.bz2,
> making it unusable).
You're right, its not a functional dependency; the full madwifi source
tree is not used directly while using madwifi-dev for the purposes
provided, but rather the full source tree *should* be used to build
binary modules to be used with the applications compiled directly
against the includes extracted from that exact same version of the
madwifi source tree.
>
> May I suggest to change "Depends: madwifi-ng-source" by something like
> "Recommends: madwifi-ng-source" ?
>
> However, I could be wrong (I am not a developer, and I have no skills
> in this field), there might be something I don't understand and a
> could reason for that dependency. In such case, just ignore this message.
>
> Thanks for maintaining the madwifi-ng experimental packages, they work
> perfectly on my systems.
Thanks for taking the time to give some valuable feedback about them.
>
> Pascal
More information about the Pkg-madwifi-maintainers
mailing list