Re: uploading distfiles directly to the distfiles mirror
On Jan 6, 2016, at 7:51 PM, Daniel J. Luke wrote: > On Jan 6, 2016, at 8:35 PM, Ryan Schmidtwrote: >> 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)? > > and probably 'sftp' instead of 'ftp' > >> Would we make a web page where people can upload a distfile for a particular >> port? > > sure, that would work too. > > I would think people's mirrors would go in a user directory too (similar to > how the svn stuff worked) - so it would be obvious that it was a > maintainer/committer sourced distfile. In that case, this is sounding like a different and separate file hosting service we could provide, not to be thought of as part of the distfile mirror. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
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 Schmidtwrote: > 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)? and probably 'sftp' instead of 'ftp' > Would we make a web page where people can upload a distfile for a particular > port? sure, that would work too. I would think people's mirrors would go in a user directory too (similar to how the svn stuff worked) - so it would be obvious that it was a maintainer/committer sourced distfile. > Would we make a new port command to submit a distfile? that could work too (and might be a nice enhancement later to make it easier on maintainers) - but I don't think we need to wait for our (long) dev/release cycle to get something working. > I don't really want to be in the business of distributing our own files. The > purpose of the mirror is to mirror files the developers provide elsewhere. Sure, in the general case we shouldn't do it - but when the developer doesn't provide a good stable file (and/or only provides source from a source control system), then the best bad option is for us to create our own distfile. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
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 that (storing lots of binaries in our svn repo isn't a great idea), > being able to upload a snapshot again would be welcome. > > It would fix this and to some extent also make it less 'necessary' for people > to have ports fetching from source control systems (giving everyone the > benefit of having the files mirrored and cacheable). 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. Would we make a web page where people can upload a distfile for a particular port? Would we make a new port command to submit a distfile? I don't really want to be in the business of distributing our own files. The purpose of the mirror is to mirror files the developers provide elsewhere. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: uploading distfiles directly to the distfiles mirror
On Jan 6, 2016, at 8:53 PM, Ryan Schmidtwrote: > On Jan 6, 2016, at 7:51 PM, Daniel J. Luke wrote: >> 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)? >> >> and probably 'sftp' instead of 'ftp' >> >>> Would we make a web page where people can upload a distfile for a >>> particular port? >> >> sure, that would work too. >> >> I would think people's mirrors would go in a user directory too (similar to >> how the svn stuff worked) - so it would be obvious that it was a >> maintainer/committer sourced distfile. > > In that case, this is sounding like a different and separate file hosting > service we could provide, not to be thought of as part of the distfile mirror. I don't have a preference for which machine it's hosted on - if we could make use of one of the existing authentication mechanisms, though, that would be great. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev