Re: [151216] contrib/buildbot-test/master.cfg

On 11 August 2016 at 08:20, Lawrence Velázquez wrote: >> On Aug 11, 2016, at 2:07 AM, Ryan Schmidt wrote: >>> On Aug 10, 2016, at 11:56 PM, Mojca Miklavec wrote: >>> >>> I changed that in r151249 and 151258. I don't know any "official" way >>> to construct PATH though and it wouldn't work on Window

Re: [151216] contrib/buildbot-test/master.cfg

> On Aug 11, 2016, at 1:20 AM, Lawrence Velázquez wrote: > >> On Aug 11, 2016, at 2:07 AM, Ryan Schmidt wrote: >> >> >>> On Aug 10, 2016, at 11:56 PM, Mojca Miklavec wrote: >>> >>> I changed that in r151249 and 151258. I don't know any "official" way >>> to construct PATH though and it woul

Re: [151216] contrib/buildbot-test/master.cfg

> On Aug 11, 2016, at 2:07 AM, Ryan Schmidt wrote: > > >> On Aug 10, 2016, at 11:56 PM, Mojca Miklavec wrote: >> >> I changed that in r151249 and 151258. I don't know any "official" way >> to construct PATH though and it wouldn't work on Windows anyway, so >> the whole point of changing this i

Re: [151215] contrib/mp-buildbot

On 11 August 2016 at 05:56, Ryan Schmidt wrote: >> On Aug 10, 2016, at 1:25 PM, Mojca Miklavec wrote: >> >> Alternatively logdir could simply remain hardcoded as >> ${option_workdir}/logs. There's no need for an extra layer of >> complexity that doesn't really serve anyone. > > Yeah the log directo

Re: [151216] contrib/buildbot-test/master.cfg

> On Aug 10, 2016, at 11:56 PM, Mojca Miklavec wrote: > > I changed that in r151249 and 151258. I don't know any "official" way > to construct PATH though and it wouldn't work on Windows anyway, so > the whole point of changing this is a bit moot. > > Figuring out why >workdir=os.path.join(

Re: [151216] contrib/buildbot-test/master.cfg

On 11 August 2016 at 03:45, Ryan Schmidt wrote: >> On Aug 10, 2016, at 8:44 PM, Lawrence Velázquez wrote: >>> On Aug 10, 2016, at 9:37 PM, Ryan Schmidt wrote: >>> On Aug 10, 2016, at 1:13 PM, mo...@macports.org wrote: --- contrib/buildbot-test/master.cfg2016-08-10 18:09:29 UT

Re: [151215] contrib/mp-buildbot

> On Aug 10, 2016, at 1:25 PM, Mojca Miklavec wrote: > > Alternatively logdir could simply remain hardcoded as > ${option_workdir}/logs. There's no need for an extra layer of > complexity that doesn't really serve anyone. Yeah the log directory doesn't really need to be configurable, does it? I

Re: How to discontinue ports completely (py26 deprecation) ...

On 2016-8-11 08:01 , Lawrence Velázquez wrote: On Aug 10, 2016, at 5:21 PM, Fred Wright wrote: I don't consider Python 2.6 to be "cruft". Developers need many versions of Python installed for testing, and that includes any packages that are also needed. It's annoying to have to create local

Re: How to discontinue ports completely (py26 deprecation) ...

On 2016-8-11 10:50 , Clemens Lang wrote: On Wed, Aug 10, 2016 at 04:47:25PM -0500, Ryan Schmidt wrote: On Aug 10, 2016, at 13:18, Peter Danecek wrote: However, how would we procede in this case, when we have no explicit replacement to indicate? I believe the obsolete 1.0 portgroup can accom

Re: [151216] contrib/buildbot-test/master.cfg

> On Aug 10, 2016, at 8:44 PM, Lawrence Velázquez wrote: > >> On Aug 10, 2016, at 9:37 PM, Ryan Schmidt wrote: >> >>> On Aug 10, 2016, at 1:13 PM, mo...@macports.org wrote: >>> >>> --- contrib/buildbot-test/master.cfg2016-08-10 18:09:29 UTC (rev >>> 151215) >>> +++ contrib/buildbot-t

Re: [151222] users/petr/ports

> On Aug 10, 2016, at 4:03 PM, p...@macports.org wrote: > > Revision > 151222 > Author > p...@macports.org > Date > 2016-08-10 14:03:00 -0700 (Wed, 10 Aug 2016) > Log Message > > globus: add port group > Added Paths > > • users/petr/ports/_resources/ > • users/petr/ports/_resources/

Re: [151216] contrib/buildbot-test/master.cfg

> On Aug 10, 2016, at 9:37 PM, Ryan Schmidt wrote: > >> On Aug 10, 2016, at 1:13 PM, mo...@macports.org wrote: >> >> --- contrib/buildbot-test/master.cfg 2016-08-10 18:09:29 UTC (rev 151215) >> +++ contrib/buildbot-test/master.cfg 2016-08-10 18:13:02 UTC (rev 151216) >> @@ -368,6 +368,7 @@ >> >

Re: [151216] contrib/buildbot-test/master.cfg

> On Aug 10, 2016, at 1:13 PM, mo...@macports.org wrote: > > Revision > 151216 > Author > mo...@macports.org > Date > 2016-08-10 11:13:02 -0700 (Wed, 10 Aug 2016) > Log Message > > buildbot-test: show the short log with the progress of installing dependencies > Modified Paths > > • contri

Re: How to discontinue ports completely (py26 deprecation) ...

On Wed, Aug 10, 2016 at 04:47:25PM -0500, Ryan Schmidt wrote: > On Aug 10, 2016, at 13:18, Peter Danecek wrote: > > > > However, how would we procede in this case, when we have no explicit > > replacement to indicate? > > I believe the obsolete 1.0 portgroup can accommodate this: include the > p

Re: A separate PortIndex for libc++ on older systems

On 2016-8-11 04:09 , Lawrence Velázquez wrote: On Aug 10, 2016, at 4:37 AM, Ryan Schmidt wrote: We also still need to decide how to differentiate the URLs for libc++ packages from the URLs of the existing libstdc++ packages. One suggestion was to add cxx_stdlib as a variable in archive_sites

Re: How to discontinue ports completely (py26 deprecation) ...

On Aug 10, 2016, at 2:18 PM, Peter Danecek wrote: > In the process of deprecating `py26` subports, I am just looking at > some very old python packages which were never moved to Python 2.7. It > seems that in most cases there is a "good reason" why this did not > occur. They are just not used any

Re: How to discontinue ports completely (py26 deprecation) ...

On Aug 10, 2016, at 5:21 PM, Fred Wright wrote: > I don't consider Python 2.6 to be "cruft". Developers need many > versions of Python installed for testing, and that includes any > packages that are also needed. It's annoying to have to create local > versions of portfiles solely to add versio

Re: How to discontinue ports completely (py26 deprecation) ...

On Aug 10, 2016, at 13:18, Peter Danecek wrote: > > However, how would we procede in this case, when we have no explicit > replacement to indicate? I believe the obsolete 1.0 portgroup can accommodate this: include the portgroup but don't set replaced_by. However, do first consider whether t

Re: our buildslaves' Python and bash

On Aug 10, 2016, at 5:20 PM, Ryan Schmidt wrote: > Buildbot and buildbot-slave are installed using MacPorts in a second > prefix, so they're using MacPorts python27. > > mpbb is probably using the system bash because I don't recall > installing bash, but it's no problem for us to install MacPor

Re: ports.tar update frequency on new mirror

On Aug 10, 2016, at 16:03, Clemens Lang wrote: > > Hi Ryan, > > I'm wondering what update frequency I can expect for ports.tar on the > new main mirror. > > I have a cronjob set up that regularly checks whether ports.tar has not > been updated in a while; it came in handy a couple of times becau

Re: How to discontinue ports completely (py26 deprecation) ...

On Wed, 10 Aug 2016, Sterling Smith wrote: > I am all in favor of removing cruft. However, would it be worthwhile to > ping the user email list about the ports that will be deprecated (give a > specific list), to see if anyone will complain, or is it better to just > remove them, and then when s

Re: our buildslaves' Python and bash

Hi, On Wed, Aug 10, 2016 at 04:52:02PM -0400, Lawrence Velázquez wrote: > Are the buildslaves using the OS-provided bash (for mpbb) and > MacPorts' python27 (for Buildbot), or what? It's very likely the OS-provided bash, since mpbb's shebang says /bin/bash. As for Python, I think there's a separa

Re: our buildslaves' Python and bash

On Aug 10, 2016, at 15:52, Lawrence Velázquez wrote: > > Are the buildslaves using the OS-provided bash (for mpbb) and MacPorts' > python27 (for Buildbot), or what? Buildbot and buildbot-slave are installed using MacPorts in a second prefix, so they're using MacPorts python27. mpbb is probab

ports.tar update frequency on new mirror

Hi Ryan, I'm wondering what update frequency I can expect for ports.tar on the new main mirror. I have a cronjob set up that regularly checks whether ports.tar has not been updated in a while; it came in handy a couple of times because most developers usually sync using SVN and would not notice t

our buildslaves' Python and bash

Are the buildslaves using the OS-provided bash (for mpbb) and MacPorts' python27 (for Buildbot), or what? vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [151215] contrib/mp-buildbot

Hi Mojca, a couple of review comments inline below. On Wed, Aug 10, 2016 at 11:09:30AM -0700, mo...@macports.org wrote: > Revision: 151215 > https://trac.macports.org/changeset/151215 > Author: mo...@macports.org > Date: 2016-08-10 11:09:29 -0700 (Wed, 10 Aug 2016) > Log Message:

Re: [151215] contrib/mp-buildbot

On Aug 10, 2016, at 2:25 PM, Mojca Miklavec wrote: > Thanks a lot for catching this. > > Would you be willing to fix this properly before I make a bunch of > other mistakes? In particular I'm not absolutely sure how to handle > cases like this one in an elegant way: >./mpbb something --logdi

Re: [151215] contrib/mp-buildbot

On 10 August 2016 at 20:17, Lawrence Velázquez wrote: > > --- contrib/mp-buildbot/mpbb 2016-08-10 16:13:48 UTC (rev 151214) > +++ contrib/mp-buildbot/mpbb 2016-08-10 18:09:29 UTC (rev 151215) > @@ -77,6 +79,10 @@between builds. Your MacPorts installation in --prefix > needs to be able to >

Re: How to discontinue ports completely (py26 deprecation) ...

Petr, I am all in favor of removing cruft. However, would it be worthwhile to ping the user email list about the ports that will be deprecated (give a specific list), to see if anyone will complain, or is it better to just remove them, and then when someone complains tell them how to go back t

How to discontinue ports completely (py26 deprecation) ...

Hi all, In the process of deprecating `py26` subports, I am just looking at some very old python packages which were never moved to Python 2.7. It seems that in most cases there is a "good reason" why this did not occur. They are just not used anymore. Some of these packages are deprecated ex

Re: [151215] contrib/mp-buildbot

On Aug 10, 2016, at 2:09 PM, mo...@macports.org wrote: > Revision > 151215 Author > mo...@macports.org Date > 2016-08-10 11:09:29 -0700 (Wed, 10 Aug 2016) > Log Message > > mp-buildbot: create a lo

Re: A separate PortIndex for libc++ on older systems

On Aug 10, 2016, at 4:37 AM, Ryan Schmidt wrote: > We also still need to decide how to differentiate the URLs for libc++ > packages from the URLs of the existing libstdc++ packages. One suggestion was > to add cxx_stdlib as a variable in archive_sites.conf, and upload the libc++ > archives wit

Re: Determine before installation whether a port can be installed

On 27 July 2016 at 06:09, Ryan Schmidt wrote: > > One solution that occurs to me is to define a new "preflight" phase, to be > run before dependencies are computed. Ports can override that phase and do > whatever checks they need and exit with "return -code error" if needed. This > seems like th

port install v port mpkg | mdmg

Hi: Is it possible for a port to take different actions depending on whether the user has initiated ‘port install’ v. 'port mpkg’ (or ‘port mdmg’)? My mythtv-pkg.27 is intended to be used to create an all-in-one installer package for MythTV. I have a VM with a custom prefix for this. The resu

A separate PortIndex for libc++ on older systems

On Jul 31, 2016, at 3:25 AM, dev...@macports.org wrote: > Revision > 150854 > Author > dev...@macports.org > Date > 2016-07-31 01:25:57 -0700 (Sun, 31 Jul 2016) > Log Message > > gnome-maps: update to version 3.20.2, 3.18.3 for systems that don't support > libc++, now uses maps from MapBox. > Mo