Re: Updating unmaintained ports (was: Re: Get date of Portfile)

2010-04-18 Thread Ryan Schmidt
(Moving discussion to macports-dev from macports-users) On Apr 17, 2010, at 03:49, Scott Haneda wrote: > This seems to be the most common of the expressions used: >(\d+(?:\.\d+)*) > Has that been determined the preferred method of making that match? I believe that's part of the livecheck.re

Re: Updating unmaintained ports (was: Re: Get date of Portfile)

2010-04-18 Thread Ryan Schmidt
On Apr 18, 2010, at 03:26, Ryan Schmidt wrote: >> Could you walk me through port "mowitz" >> I look at that Portfile and I see the download url is: >> http://siag.nu/pub/mowitz/ >> If I go to that url, it is 404, I then combine it all to test it: >> http://siag.nu/pub/mowitz/Mowitz-0.3.1 >>

Re: [66600] trunk/base/src/macports1.0/macports_fastload.tcl.in

2010-04-18 Thread Joshua Root
On 2010-4-18 12:31 , Ryan Schmidt wrote: > > On Apr 17, 2010, at 21:10, rai...@macports.org wrote: > >> Avoid catch which masks any error, instead test if the file actually exists > > I was gonna ask about this, with regard to the python portgroups. Shouldn't > we be doing this: > > > > $ sv

Re: Updating unmaintained ports: alphamail

2010-04-18 Thread Ryan Schmidt
On Apr 18, 2010, at 03:26, Ryan Schmidt wrote: > On Apr 17, 2010, at 03:49, Scott Haneda wrote: > >> Would you mind walking me through your process of one port, so I know how to >> do this in a fast way. > > Ok, let me pick one from my to-do list and see what happens. Let's do another. alpha

Re: Updating unmaintained ports: ample

2010-04-18 Thread Ryan Schmidt
Here's a simple one where we just need to fix the livecheck. ample seems to have been updated (port version: 0.5.7, new version: 0.4.0) I don't find any tickets, the homepage seems to be current, version 0.5.7 is the latest and was released in 2003. The project is hosted at SourceForge and uses

Re: Updating unmaintained ports: alphamail

2010-04-18 Thread Joseph Holsten
Ryan Schmidt wrote: > Let's do another. > > alphamail seems to have been updated (port version: 1.0.16, new version: 1.05) [snip a tale of shaved yaks] > That's all I can do for this one for now. > > Not sure if any of this is being helpful to you. Each port has its own story > and its own needs

Re: Updating unmaintained ports

2010-04-18 Thread Rainer Müller
On 2010-04-18 10:26 , Ryan Schmidt wrote: > My favorite livecheck which you've probably seen me add to many ports > is: > > livecheck.type regex livecheck.regex ${name}-(\[0-9.\]+)\\.tar > > This checks the project's homepage (the default livecheck.url is > ${homepage}); this works great if they

Re: [66590] trunk/dports/devel

2010-04-18 Thread Thomas Keller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 18.04.10 04:21, schrieb Ryan Schmidt: > On Apr 17, 2010, at 17:12, Thomas Keller wrote: >> Am 18.04.10 00:04, schrieb Rainer Müller: >>> But I would encourage to use some more recent version of python. >>> I would choose ${prefix}/bin/python2.6 and

Re: [66590] trunk/dports/devel

2010-04-18 Thread Ryan Schmidt
On Apr 18, 2010, at 10:04, Thomas Keller wrote: > It seems as if py26-gtk needs py26-cairo, which needs py26-numpy, which > ends up needing gcc43. True, though py26-numpy has a +no_gcc43 variant you can use if you want to skip the parts that need a Fortran compiler. > I went through without ins

Re: How to find out how often a port file has been downloaded?

2010-04-18 Thread Bradley Giesbrecht
On Apr 17, 2010, at 5:48 PM, Ryan Schmidt wrote: On Apr 17, 2010, at 18:55, Marko Käning wrote: I was just thinking that it might be helpful to know which ports are most actively used by the community. Is there a way to determine how often ports got actually installed? That would be perh

Re: How to find out how often a port file has been downloaded?

2010-04-18 Thread Jeremy Lavergne
Just make it opt in. "Bradley Giesbrecht" wrote: > >On Apr 17, 2010, at 5:48 PM, Ryan Schmidt wrote: > >> >> On Apr 17, 2010, at 18:55, Marko Käning wrote: >> >>> I was just thinking that it might be helpful to know which ports >>> are most actively used by the community. >>> >>> Is there a wa

Re: Updating unmaintained ports: alphamail

2010-04-18 Thread Bradley Giesbrecht
On Apr 18, 2010, at 2:51 AM, Ryan Schmidt wrote: Let's do another. alphamail seems to have been updated (port version: 1.0.16, new version: 1.05) That doesn't look right. Tickets? Yes, one: http://trac.macports.org/ticket/15383 That ticket updates the port to 1.0.44, so now we know the

Re: Updating unmaintained ports: alphamail

2010-04-18 Thread Rainer Müller
On 2010-04-18 18:08 , Bradley Giesbrecht wrote: > I would like port -v livecheck to report the current mp version and > the highest source version found although I wouldn't put a much of > priority on it. But is one were to implement the master_sites patch > from Rainer maybe consider this en

Re: Updating unmaintained ports: alphamail

2010-04-18 Thread Joshua Root
On 2010-4-19 02:08 , Bradley Giesbrecht wrote: > > My experience is that "port livecheck" without -d will report nothing if > livecheck is invalid for various reason, example distname has changed or > source repository has moved. I usually do port -d livecheck. You always get an error message if

Re: Updating unmaintained ports: alphamail

2010-04-18 Thread Bradley Giesbrecht
On Apr 18, 2010, at 9:59 AM, Joshua Root wrote: On 2010-4-19 02:08 , Bradley Giesbrecht wrote: My experience is that "port livecheck" without -d will report nothing if livecheck is invalid for various reason, example distname has changed or source repository has moved. I usually do port

Re: Updating unmaintained ports: alphamail

2010-04-18 Thread Ryan Schmidt
On Apr 18, 2010, at 12:12, Bradley Giesbrecht wrote: > On Apr 18, 2010, at 9:59 AM, Joshua Root wrote: > >> On 2010-4-19 02:08 , Bradley Giesbrecht wrote: >>> >>> My experience is that "port livecheck" without -d will report nothing if >>> livecheck is invalid for various reason, example distna

Re: How to find out how often a port file has been downloaded?

2010-04-18 Thread Marko Käning
> This could be very valuable, if it was determined that what most think is an > obscure port was heavily used, it could be looked at more closely, and > perhaps made as perfect as could be as far as ease of install, up to > date'ness etc. Yep ... > My gut tells me Apache, php, and MySql are at