On 2012-1-3 18:47 , Ryan Schmidt wrote:
>
> On Dec 26, 2011, at 16:53, Ryan Schmidt wrote:
>
>> Looking on the main distfiles mirror, I see we do not have any distfiles
>> there for molden, but we do have some for metis. If we're not supposed to be
>> distributing metis, we need to fix the scri
On Dec 26, 2011, at 16:53, Ryan Schmidt wrote:
> Looking on the main distfiles mirror, I see we do not have any distfiles
> there for molden, but we do have some for metis. If we're not supposed to be
> distributing metis, we need to fix the script(s) and delete these files from
> all mirrors.
On 2011-12-29 11:16 , Dan Ports wrote:
> On Mon, Dec 26, 2011 at 08:36:15PM -0600, Ryan Schmidt wrote:
>> (How does the buildbot / gathering distributable archives / checking if the
>> license is valid stuff work? Does that auto-update, if I commit a new
>> approved license name to port_binary_di
On Mon, Dec 26, 2011 at 08:36:15PM -0600, Ryan Schmidt wrote:
> (How does the buildbot / gathering distributable archives / checking if the
> license is valid stuff work? Does that auto-update, if I commit a new
> approved license name to port_binary_distributable.tcl?)
I can't answer the rest o
On Dec 26, 2011, at 6:36 PM, Ryan Schmidt wrote:
>
> On Dec 26, 2011, at 20:02, William Siegrist wrote:
>
>> Both scripts are used. The first runs periodically and the second runs after
>> each commit. The exclusion lists are kept in sync manually on the server,
>> but the scripts in the repo
On Dec 26, 2011, at 20:02, William Siegrist wrote:
> Both scripts are used. The first runs periodically and the second runs after
> each commit. The exclusion lists are kept in sync manually on the server, but
> the scripts in the repo are just examples and not used to update the server
> copi
On Dec 26, 2011, at 2:53 PM, Ryan Schmidt wrote:
> I would like to add some mirroring exclusions for some ports that aren't
> committed yet, whose distfiles we're not allowed to redistribute, but I don't
> quite understand how we're doing that.
>
> I see we have these two scripts:
>
> https://
I would like to add some mirroring exclusions for some ports that aren't
committed yet, whose distfiles we're not allowed to redistribute, but I don't
quite understand how we're doing that.
I see we have these two scripts:
https://trac.macports.org/browser/trunk/base/portmgr/jobs/mirror_macport
