On Aug 21, 2015, at 8:22 PM, Chunyang Xu wrote: > > On Sat, Aug 22, 2015 at 8:30 AM, Ryan Schmidt wrote: >> >>> On Aug 21, 2015, at 5:46 PM, [email protected] wrote: >>> >>> Revision >>> 139623 >>> Author >>> [email protected] >>> Date >>> 2015-08-21 15:46:10 -0700 (Fri, 21 Aug 2015) >>> Log Message >>> >>> proxychains-ng: new port, version 4.10 >>> Added Paths >>> >>> • trunk/dports/devel/proxychains-ng/ >>> • trunk/dports/devel/proxychains-ng/Portfile >>> Diff >>> >>> Added: trunk/dports/devel/proxychains-ng/Portfile (0 => 139623) >>> >>> --- trunk/dports/devel/proxychains-ng/Portfile >>> (rev 0) >>> +++ trunk/dports/devel/proxychains-ng/Portfile 2015-08-21 22:46:10 >>> UTC (rev 139623) >>> >>> @@ -0,0 +1,25 @@ >>> >>> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; >>> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 >>> +# $Id$ >>> + >>> +PortSystem 1.0 >>> +PortGroup github 1.0 >>> + >>> +github.setup rofl0r proxychains-ng 4.10 v >>> +maintainers chunyang openmaintainer >>> +categories devel >>> +license GPL-2 >>> +description hook preloader >>> +long_description ${name} is a ${description} which hooks calls to \ >>> + sockets indynamically linked programs and redirects \ >>> + it through one or more socks/http proxies. >>> + >>> +platforms darwin >>> + >>> +master_sites ${homepage}/archive/ >>> +distname ${github.tag_prefix}${version} >>> +worksrcdir ${name}-${version} >> >> Is there a specific reason why you overrode the github portgroup's defaults >> here? > > I was unable to fetch that tarball through the default url when I was > creating the portfile, but I just tried again and it worked now, I > don't know why it didn't work before, maybe because of my network > issue. I will remove these and update checksum soon.
Probably best to wait until the next version update, because otherwise you're making people (and our servers) download a second copy of 4.10 for no real reason. Also, you have to follow the stealth-update recipe which is more unnecessary complication. I just wanted to make sure there was no other issue going on here. Related: https://trac.macports.org/ticket/40518 _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
