First, you should give a name to the master site:
variant somedata {
master_sites-append http://example.com:foo
distfiles-append file1:foo file2:foo ...
...
}
This way port won't try to fetch the extra distfiles from the main
master site.
For the extract phase, you need to set extract.only before appending new
distfiles:
variant somedata {
...
eval extract.only ${distfiles}
distfiles-append ...
}
On a last note, you don't need to separate the checksums of the
distfiles appended by the variant
from those of the main distfile, I think keeping checksums together is
easier on the eyes and brain:
checksums [suffix ${distname}] \
checksums of the main distfile
extra_file_1 \
... \
extra_file_2 \
... \
...
Le 8 mai 09 à 01:46, Darren Weber a écrit :
OK, so all the files and checksums are in the variant (using append
clauses), but the extract phase should not work on these data
files. Will something like this work:
variant somedata {
master_sites-append http://extraDataFileURL/
distfiles-append aBunchOfDataFiles
checksums-append yadda yadda ;-)
extract {}
post-destroot {
# use tar on the $distfiles to extract all the data somewhere
useful
}
}
Thanks in advance,
Darren
On Thu, May 7, 2009 at 4:21 PM, nox <[email protected]> wrote:
Bad idea. Every fetched file need to have its checksums verified.
If you have the checksums, you inevitably also have the filenames
and thus do not have to use a glob pattern.
If you don't have fhe filenames, then you don't have the checksums.
Regards.
Le 8 mai 09 à 01:07, Darren Weber a écrit :
For a variant in the InsightToolkit, it would be useful to get all
the data files from here:
http://public.kitware.com/pub/itk/Data/BrainWeb/
ie: <snip/>
Is it possible to specify a fetch filename alias to get all the
files like "BrainPart*.tgz"?
Would you override the fetch phase in a variant, maybe something like:
variant braindata {
fetch {
exec wget -r -l1 --no-parent -A.tgz
http://public.kitware.com/pub/itk/Data/BrainWeb/
# some code to put these downloads in the right place, like $
{distfiles}
}
}
Thanks in advance,
Darren
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
