On Jul 2, 2013, at 2:16 PM, Mojca Miklavec <[email protected]> wrote:
> On Tue, Jul 2, 2013 at 7:10 PM, Bradley Giesbrecht wrote:
>> On Jul 2, 2013, at 10:03 AM, Lawrence Velázquez wrote:
>>> It's a little weird to put stuff into ${destroot} during extract. I
>>> certainly do not expect "port extract" to create the destroot.
>>
>> Yes, it is not common though they are simply data files, no configure, make
>> or make install; so I understand why Mojca questions the need to copy large
>> data sets around.
>>
>> One could set "extract {}", let destroot make directories and code the
>> extraction. I thought making use of port extract was a nicer way.
>
> But then others will argue that users expect from "extract" to check
> the checksums and actually extract something. I let the gurus figure
> out the best way. I can live with moving files around if that's really
> needed or expected.
I'd suggest letting extract do its thing and moving the data files in destroot.
Moving (as opposed to copying) should be an inexpensive operation.
vq
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
