Adding fetch.type git as a variant?

[Bradley Giesbrecht]

On May 10, 2011, at 2:32 AM, Bayard Bell wrote:

> I'd add to that that it seems to make for undue confusion to use a variant to follow a different version.
> 
> On 10 May 2011, at 01:11, Joshua Root wrote:
> 
>> On 2011-5-10 08:34 , David Bruce wrote:
>>> Hi,
>>> 
>>> All of the SCM fetch types are discouraged in the manual for
>>> "non-reproducible builds", which is fair enough.  But as the
>>> maintainer of both the Portfile and the upstream project, it seems it
>>> would be highly useful to have an automated way to see if the latest
>>> git source breaks the macports build.  Is it possible/advisable to do
>>> this as a variant, as there doesn't seem to be any option to tell port
>>> to use a different fetch type, e.g. something like:
>>> 
>>> variant git_dev_only description {use latest git source} {
>>>    fetch.type          git
>>>    git.url                git://git.debian.org/git/tux4kids/t4k_common.git
>>>    use_autoreconf  yes
>>> }
>>> 
>>> plus whatever else is needed to get it to work.
>>> 
>>> Thanks for any advice,
>>> 
>>> David Bruce
>> 
>> I don't think this would be appropriate for inclusion in the main repo.
>> You could add this variant to your local copy, or you could have a
>> script that runs something like
>> 'port destroot myport fetch.type=git use_autoreconf=yes ...'

There are a number of {port_name}-devel ports that use SCM systems as sources.

$ for port in $(port echo name:-devel$);do port cat $port | grep fetch.type | xargs echo $port;done


Regards,
Bradley Giesbrecht (pixilla)