Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On 8 January 2016 at 01:47, Ryan Schmidt wrote: > On Jan 7, 2016, at 12:12 PM, Eric A. Borisch wrote: > >> Bringing this back to the original point, it looks like there was some >> discussion (I think) in this thread of making alocation (possibly >> integrated in terms of access accounts with svn

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

Another solution would be a PR with a patch for https://github.com/python/docsbuild-scripts/blob/master/build_docs.py to add versions, I guess. Russell On 08/01/16 09:11, Mojca Miklavec wrote: On 8 January 2016 at 01:47, Ryan Schmidt wrote: On Jan 7, 2016, at 12:12 PM, Eric A. Borisch

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On 2016-1-8 05:12 , Eric A. Borisch wrote: > Bringing this back to the original point, it looks like there was some > discussion (I think) in this thread of making alocation (possibly > integrated in terms of access accounts with svn commit access) > available to store a 'snapshot' of a 'distfile'

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On Jan 7, 2016, at 12:12 PM, Eric A. Borisch wrote: > Bringing this back to the original point, it looks like there was some > discussion (I think) in this thread of making alocation (possibly > integrated in terms of access accounts with svn commit access) > available to store a 'snapshot' of a

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On 06/01/16 23:44, Ryan Schmidt wrote: On Jan 6, 2016, at 4:44 AM, Russell Jones wrote: I was thinking you might use git+https://github.com/python/cpython.git/Doc with a set checkout id using the GitHub PortGroup, but that would require building the docs. How about using

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On 07/01/16 16:17, Daniel J. Luke wrote: On Jan 7, 2016, at 5:53 AM, Russell Jones wrote: On Daniel's point: checking an SSL cert provides a guarantee from some certificate issuer, given a competent sysadmin, etc, that the host name matches it. When you

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On Jan 7, 2016, at 5:53 AM, Russell Jones wrote: > On Daniel's point: checking an SSL cert provides a guarantee from some > certificate issuer, given a competent sysadmin, etc, that the host name > matches it. When you validate an SSL certificate all you end up

Re: SSL Certificates (was Re: [144262] trunk/dports/lang/py-htmldocs/Portfile)

On 07/01/16 16:44, Daniel J. Luke wrote: On Jan 7, 2016, at 11:41 AM, Russell Jones wrote: On 07/01/16 16:17, Daniel J. Luke wrote: On Jan 7, 2016, at 5:53 AM, Russell Jones wrote: On Daniel's point: checking an SSL cert

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

Hi, On Thu, Jan 07, 2016 at 12:12:20PM -0600, Eric A. Borisch wrote: > Bringing this back to the original point, it looks like there was some > discussion (I think) in this thread of making alocation (possibly > integrated in terms of access accounts with svn commit access) > available to store a

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

I was thinking you might use git+https://github.com/python/cpython.git/Doc with a set checkout id using the GitHub PortGroup, but that would require building the docs. How about using https://docs.python.org and relying on python.org's SSL cert to ensure the integrity rather than the MacPorts

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

The general solution to this problem is to create a stable (snapshot) mirror somewhere else. > On Jan 6, 2016, at 5:44 AM, Russell Jones > wrote: > I was thinking you might use git+https://github.com/python/cpython.git/Doc > with a set checkout id using the

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On Jan 6, 2016, at 4:44 AM, Russell Jones wrote: > I was thinking you might use git+https://github.com/python/cpython.git/Doc > with a set checkout id using the GitHub PortGroup, but that would require > building the docs. > > How about using https://docs.python.org and relying on

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

On Jan 6, 2016, at 6:44 PM, Ryan Schmidt wrote: > An SSL certificate does not guarantee the user is getting the same files the > maintainer did. It only guarantees the user is talking to the same server. it's not even that strong of a guarantee (especially since the

Re: uploading distfiles directly to the distfiles mirror (was: Re: [144262] trunk/dports/lang/py-htmldocs/Portfile)

On Jan 6, 2016, at 8:35 PM, Ryan Schmidt wrote: > How would you envision this capability being provided? I wouldn't want to, > for example, just open up ftp write access to the distfiles server to anyone > who asked for it. maybe for maintainers (or committers only)?

Re: uploading distfiles directly to the distfiles mirror (was: Re: [144262] trunk/dports/lang/py-htmldocs/Portfile)

On Jan 6, 2016, at 7:29 PM, Daniel J. Luke wrote: > > Can we make it easier for maintainers to add files to the mirrors? When we > used to put files into subversion, it was easy for any maintainer to avoid > this problem by just checking in a snapshot. While it's undesirable to go > back to

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

Hi, On Tue, Jan 05, 2016 at 12:44:49PM -0600, Ryan Schmidt wrote: > > I'm not comfortable with installing unchecked files on user systems. > The whole point of the checksum system is to verify that the files > that are installed on user systems are the same files that were tested > by the

Re: [144262] trunk/dports/lang/py-htmldocs/Portfile

> On Jan 5, 2016, at 12:43 PM, ebori...@macports.org wrote: > > Revision > 144262 > Author > ebori...@macports.org > Date > 2016-01-05 10:43:29 -0800 (Tue, 05 Jan 2016) > Log Message > > py-htmldocs: 34 and 35 tarballs appear to be updated nightly; skip checksums. > (At least we don't install