Even with support for "release" github feature in github-portgroup the portfile wouldn't be simpler, I find portfiles calling github.setup harder to read than those with name, version, homepage and master_sites variables clearly declared.
On Thu, Mar 27, 2014 at 12:16 AM, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Mar 24, 2014, at 04:58, and.dam...@macports.org wrote: > >> Revision >> 118163 >> Author >> and.dam...@macports.org >> Date >> 2014-03-24 02:58:12 -0700 (Mon, 24 Mar 2014) >> Log Message >> >> port bitcoin: switch from git fetching to tarball release, allows to cache >> local distfile; openmaintainer >> Modified Paths >> >> • trunk/dports/finance/bitcoin/Portfile >> Diff >> >> Modified: trunk/dports/finance/bitcoin/Portfile (118162 => 118163) >> >> --- trunk/dports/finance/bitcoin/Portfile 2014-03-24 09:53:36 UTC (rev >> 118162) >> +++ trunk/dports/finance/bitcoin/Portfile 2014-03-24 09:58:12 UTC (rev >> 118163) >> >> @@ -16,9 +16,11 @@ >> >> operating through the nodes of the network. >> >> homepage http://www.bitcoin.org/ >> >> >> -fetch.type git >> -git.url >> https://github.com/bitcoin/bitcoin.git >> >> -git.branch v${version} >> >> +master_sites https://github.com/[string >> repeat "$name/" 2]archive/ >> +distname v${version} >> +worksrcdir ${name}-${version} > > Could we simplify this by using the github portgroup? > > > -- Andrea _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev