Date: Sat, 11 Aug 2018 08:11:53 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: David Naylor <dbn@freebsd.org>, Mathieu Arnold <mat@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r476822 - in head/devel: . py-knack Message-ID: <6731ba07-ac70-fe0a-9460-dce3f321c091@FreeBSD.org> In-Reply-To: <27890694.glqiyieaPB@dragon.local> References: <201808100943.w7A9h8od064813@repo.freebsd.org> <20180810120411.ljask2jauziadfzk@atuin.in.mat.cc> <27890694.glqiyieaPB@dragon.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/08/2018 4:28 am, David Naylor wrote: > On Friday, 10 August 2018 14:04:11 SAST Mathieu Arnold wrote: >> On Fri, Aug 10, 2018 at 09:43:08AM +0000, David Naylor wrote: >>> +PORTNAME= knack >>> +DISTVERSION= 0.4.2 >>> +USE_GITHUB= yes >>> +GH_ACCOUNT= Microsoft >> >> Why use an extract from github? There seems to be a perfectly good >> released tarball: > > Initially, it was because I came upon the port via GitHub. However, I stuck > with GitHub because it appears (anecdotally) PortScout does not pick up new > releases from PyPi [1][2]. > > If you prefer, I can switch this (and py-applicationinsights) over to PyPi? > It does, however, make my life a lot easier when portscout works. I use it to > monitor for version updates for most of the ports I maintain. > > Regards > > David > > [1] https://pypi.org/project/msrest/#files > [2] https://portscout.freebsd.org/sunpoet@freebsd.org.html > Portscout works for PyPI [1]. If it breaks (or is broken) we'll fix it. Python@ prefers people use PyPI by default unless there's a compelling temporary case to use an alternative, such as test files/data files missing. This way the upstreams entire packaging pipeline is tested, and it's the same thing people get when they pip install. [1] http://svnweb.freebsd.org/changeset/ports/401037
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6731ba07-ac70-fe0a-9460-dce3f321c091>