how to control distfile extraction

[Darren Weber]

In a prior thread, a solution to control distfile extraction was discussed,
using extract.only, e.g.:

variant data description {install example data [default: ${vtkDataPath}]} {
    eval extract.only   ${distfiles}
    distfiles-append    ${vtkDataFile}
    checksums-append    ${vtkDataFile} \
                            md5  283d40f3e499b3a6102d86855d2ca20b \
                            sha1 a710227e7f7f25f481a36d2fa14bda49756bd39d \
                            rmd160 160129a0580bd7b70b40d3f7fa61bbd78b586ad8
}

variant doc description {provide doxygen documentation [default:
${vtkDocPath}]} {
    eval extract.only   ${distfiles}
    distfiles-append    ${vtkDocFile}
    checksums-append    ${vtkDocFile} \
                            md5 eb8fcaa5fa8bc8f463084f071b2b978b \
                            sha1 1a8f8ff20b18bc7ac707846a8ba056b04c827392 \
                            rmd160 c657f9ce0850eca1bb0a0d7537f0bcf631132f30
}

I have the two variants defined above (plus additional post-destroot
statements).  It appears that the data distfile is still extracted.  Is it
true that the 'eval extract.only' statement can be used and effective in
multiple variants? The idea here is not to extract any of the data or doc
distfiles.

Thanks,
Darren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20090512/931bc106/attachment.html>