Re: MacPorts Statistics
On Mar 28, 2014, at 7:03 PM, Craig Treleaven wrote: > Branching the subject a little, perhaps, but... > > Looking at the statistics page for a particular port, say libpng: > > http://stats.macports.neverpanic.de/categories/22/ports/2455 > > This has a lot of information that a user might be interested in before > installing a port. Right now, the port search page on the web leads to the > Portfile, eg: > > https://trac.macports.org/browser/trunk/dports/graphics/libpng/Portfile > > which isn't the prettiest advertisement for a piece of software. > > To me, the web search should give the potential user enough information to > decide if whether to install the package or not. A rough draft would be: > > = > From Portfile: > -port/subport name (link to Portfile) > -categories > -version/revision > -long_description > -variants (list with descriptions) > -homepage (as link) > -license > -platforms > -supported_archs > -dependencies (as links to other port pages; bonus marks if it could > link to an rdeps graph!) > > From statistics: >> # reported installs > -requested/ last week, 1 month ago, 1 year ago > -installed as dependency / last week, 1 month ago, 1 year ago > -rank of reported installs, requested, last week: xxx of 18,312 > -link to page with more detailed statistics > > From buildbots or package server (if possible): >> Dates of most recent builds > -version built / Mavericks, Mtn Lion, Lion, Snow Leopard > Eg: > 1.2.3_4 yesterday yesterday failed unsupported > (indicator if unsuccessful, not supported on that OS) > = > > I don't know if the last section is even possible. Would likely require the > buildbots to update a database at the end of each build? > > Thoughts? I like the idea. I'm sure this is implied by your above text but it might be nice to have the build bots have mpstats installed by default to participate in the statistics. Regards, Bradley Giesbrecht (pixilla) ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts Statistics
Branching the subject a little, perhaps, but... Looking at the statistics page for a particular port, say libpng: http://stats.macports.neverpanic.de/categories/22/ports/2455 This has a lot of information that a user might be interested in before installing a port. Right now, the port search page on the web leads to the Portfile, eg: https://trac.macports.org/browser/trunk/dports/graphics/libpng/Portfile which isn't the prettiest advertisement for a piece of software. To me, the web search should give the potential user enough information to decide if whether to install the package or not. A rough draft would be: = From Portfile: -port/subport name (link to Portfile) -categories -version/revision -long_description -variants (list with descriptions) -homepage (as link) -license -platforms -supported_archs -dependencies (as links to other port pages; bonus marks if it could link to an rdeps graph!) From statistics: # reported installs -requested/ last week, 1 month ago, 1 year ago -installed as dependency / last week, 1 month ago, 1 year ago -rank of reported installs, requested, last week: xxx of 18,312 -link to page with more detailed statistics From buildbots or package server (if possible): Dates of most recent builds -version built / Mavericks, Mtn Lion, Lion, Snow Leopard Eg: 1.2.3_4 yesterday yesterday failed unsupported (indicator if unsuccessful, not supported on that OS) = I don't know if the last section is even possible. Would likely require the buildbots to update a database at the end of each build? Thoughts? Craig ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [118284] trunk/dports/devel/wemux/Portfile
The default patch phase patches files in ${patch.dir} (and the default for
${patch.dir} is ${worksrcpath}), but there is no guarantee about what the
current directory will be when you run a Tcl command in a portfile; that, along
with the “cd” Tcl command for changing the current directory, were removed from
MacPorts something like 6 years ago. You’re now supposed to specify all paths
absolutely, or, on commands like system, reinplace and xinstall where it’s
available, use the -W argument.
On Mar 28, 2014, at 16:49, Aljaž 'g5pw' Srebrnič wrote:
> Thanks! Why is that, though? Isn’t the patch phase evaluated with worksrcdir
> as current directory?
>
> On 28 marzo 2014 at 22:46:53, Ryan Schmidt wrote:
>
>>
>> On Mar 28, 2014, at 16:31, g...@macports.org wrote:
>>
>> > Revision
>> > 118284
>> > Author
>> > g...@macports.org
>> > Date
>> > 2014-03-28 14:31:27 -0700 (Fri, 28 Mar 2014)
>> > Log Message
>> >
>> > devel/wemux:
>> > fix conf file location (closes #43096)
>> > change prefix in documentation, too.
>> >
>> > Modified Paths
>> >
>> > • trunk/dports/devel/wemux/Portfile
>>
>>
>> > @@ -23,7 +23,7 @@
>> > use_configure no
>> >
>> > patch {
>> > - reinplace "s|/etc/wemux|${prefix}&|g" ${worksrcpath}/wemux
>> > + reinplace "s|/usr/local|${prefix}|g" wemux README.md man/wemux.1
>> > }
>> >
>> > build {}
>>
>> You should not assume that the current directory is ${worksrcpath}; you
>> should specify it, e.g. by using “reinplace -W ${worksrcpath} …”.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [118284] trunk/dports/devel/wemux/Portfile
Thanks! Why is that, though? Isn’t the patch phase evaluated with worksrcdir as
current directory?
On 28 marzo 2014 at 22:46:53, Ryan Schmidt (ryandes...@macports.org) wrote:
On Mar 28, 2014, at 16:31, g...@macports.org wrote:
> Revision
> 118284
> Author
> g...@macports.org
> Date
> 2014-03-28 14:31:27 -0700 (Fri, 28 Mar 2014)
> Log Message
>
> devel/wemux:
> fix conf file location (closes #43096)
> change prefix in documentation, too.
>
> Modified Paths
>
> • trunk/dports/devel/wemux/Portfile
> @@ -23,7 +23,7 @@
> use_configure no
>
> patch {
> - reinplace "s|/etc/wemux|${prefix}&|g" ${worksrcpath}/wemux
> + reinplace "s|/usr/local|${prefix}|g" wemux README.md man/wemux.1
> }
>
> build {}
You should not assume that the current directory is ${worksrcpath}; you should
specify it, e.g. by using “reinplace -W ${worksrcpath} …”.
--
Aljaž Srebrnič a.k.a g5pw
My public key: http://bit.ly/g5pw_pubkey___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [118284] trunk/dports/devel/wemux/Portfile
On Mar 28, 2014, at 16:31, g...@macports.org wrote:
> Revision
> 118284
> Author
> g...@macports.org
> Date
> 2014-03-28 14:31:27 -0700 (Fri, 28 Mar 2014)
> Log Message
>
> devel/wemux:
> fix conf file location (closes #43096)
> change prefix in documentation, too.
>
> Modified Paths
>
> • trunk/dports/devel/wemux/Portfile
> @@ -23,7 +23,7 @@
> use_configure no
>
> patch {
> -reinplace "s|/etc/wemux|${prefix}&|g" ${worksrcpath}/wemux
> +reinplace "s|/usr/local|${prefix}|g" wemux README.md man/wemux.1
> }
>
> build {}
You should not assume that the current directory is ${worksrcpath}; you should
specify it, e.g. by using “reinplace -W ${worksrcpath} …”.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Any news on this, Shree? - Josh On 2014-3-18 06:43 , Shreeraj Karulkar wrote: > > 2) Ping issue: I have reopened the ticket which IS&T had resolved earlier. > 3/17 FireWall Rules for Mac OS Forge - ICMP . Will > let you know as soon as I find out. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Josh I suppose this is not working yet? Although there is a freeze they updated the notes that traffic is not blocked.For where it is failing is it possible to get a traceroute output from the internet to any of the servers in question here ? IS&T are asking for this info to troubleshoot this furthur. Let me know if anyone can and I’ll try to find another way to figure this out. Shree Sent from my iPhone > On Mar 28, 2014, at 8:30 AM, Joshua Root wrote: > > Any news on this, Shree? > > - Josh > >> On 2014-3-18 06:43 , Shreeraj Karulkar wrote: >> >> 2) Ping issue: I have reopened the ticket which IS&T had resolved earlier. >> 3/17 FireWall Rules for Mac OS Forge - ICMP . Will >> let you know as soon as I find out. > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Yeah, still timing out from here: % ping distfiles.macports.org PING rsync.macports.org (17.251.224.217): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- rsync.macports.org ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss % ping packages.macports.org PING packages.macports.org (17.251.224.218): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- packages.macports.org ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss Whereas for hosts on the old vlan: % ping tennine-slave.macports.org PING tennine-slave.macports.org (17.251.224.88): 56 data bytes 64 bytes from 17.251.224.88: icmp_seq=0 ttl=51 time=191.023 ms 64 bytes from 17.251.224.88: icmp_seq=1 ttl=51 time=191.048 ms 64 bytes from 17.251.224.88: icmp_seq=2 ttl=51 time=190.153 ms My traceroutes: % traceroute distfiles.macports.org traceroute to rsync.macports.org (17.251.224.217), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.764 ms 0.569 ms 0.744 ms 2 * * * 3 202.7.173.17 (202.7.173.17) 27.203 ms 26.683 ms 26.390 ms 4 syd-sot-ken-crt1-ge-5-1-0.tpgi.com.au (202.7.162.173) 26.823 ms 27.561 ms 26.784 ms 5 ge5-0-5d0.cir1.seattle7-wa.us.xo.net (216.156.100.37) 170.842 ms 170.338 ms 190.400 ms 6 vb2002.rar3.sanjose-ca.us.xo.net (207.88.13.150) 201.102 ms 195.545 ms 195.612 ms 7 ae0.cir1.sanjose2-ca.us.xo.net (207.88.13.73) 188.824 ms 188.773 ms 203.992 ms 8 * * * (no response beyond this point) % traceroute packages.macports.org traceroute to packages.macports.org (17.251.224.218), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.751 ms 0.549 ms 0.902 ms 2 * * * 3 202.7.173.17 (202.7.173.17) 27.279 ms 26.940 ms 26.403 ms 4 syd-sot-ken-crt1-ge-5-1-0.tpgi.com.au (202.7.162.173) 26.769 ms 26.682 ms 26.796 ms 5 ge5-0-5d0.cir1.seattle7-wa.us.xo.net (216.156.100.37) 169.985 ms 171.049 ms 170.820 ms 6 vb2002.rar3.sanjose-ca.us.xo.net (207.88.13.150) 189.576 ms 192.616 ms 192.020 ms 7 ae0.cir1.sanjose2-ca.us.xo.net (207.88.13.73) 188.409 ms 188.706 ms 188.747 ms 8 * * * (again no response beyond this point) Same traceroute for the old vlan: % traceroute tennine-slave.macports.org traceroute to tennine-slave.macports.org (17.251.224.88), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.957 ms 0.522 ms 0.760 ms 2 * * * 3 202.7.173.17 (202.7.173.17) 27.554 ms 31.540 ms 26.083 ms 4 syd-sot-ken-crt1-ge-5-1-0.tpgi.com.au (202.7.162.173) 26.376 ms 26.652 ms 26.811 ms 5 ge5-0-5d0.cir1.seattle7-wa.us.xo.net (216.156.100.37) 170.386 ms 170.570 ms 170.400 ms 6 vb2002.rar3.sanjose-ca.us.xo.net (207.88.13.150) 197.196 ms 191.015 ms 192.001 ms 7 ae0.cir1.sanjose2-ca.us.xo.net (207.88.13.73) 188.791 ms 188.689 ms 188.796 ms 8 * * * so I guess this may not actually be very helpful? :( - Josh On 2014-3-29 03:14 , Shreeraj Karulkar wrote: > Josh > I suppose this is not working yet? Although there is a freeze they updated > the notes that traffic is not blocked.For where it is failing is it possible > to get a traceroute output from the internet to any of the servers in > question here ? IS&T are asking for this info to troubleshoot this furthur. > > Let me know if anyone can and I’ll try to find another way to figure this > out. > Shree > > Sent from my iPhone > >> On Mar 28, 2014, at 8:30 AM, Joshua Root wrote: >> >> Any news on this, Shree? >> >> - Josh >> >>> On 2014-3-18 06:43 , Shreeraj Karulkar wrote: >>> >>> 2) Ping issue: I have reopened the ticket which IS&T had resolved earlier. >>> 3/17 FireWall Rules for Mac OS Forge - ICMP . Will >>> let you know as soon as I find out. >> > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
naming of python scripts ...
Hi all, I am realising, that some python packages which also install scripts in `bin` provide also version dependent names. For example py27-coverage (which I am looking at) is providing apart from `coverage` also `coverage2` and `coverage-2.7`. In combination with Macports Portgroup which places these scripts end in /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/ and links with version postfix are created. This leads to quite weird names link; - coverage-2.7 - coverage2-2.7 - coverage-2.7-27 So wouldn't it be decidable that the Portgroup removes these additional scripts (only differing by a version postfix before the links are created? Thanks! ~petr smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
