I don't know anything about the GSoC project, but it seems like it
would be fairly straightforward to process the webserver logs to see
what people are upgrading. Something like this:
-regexp out lines with requested package names
-cut out everything but the package name/arch/etc.
-sort by name
-
> When someone evaluates the work and determines it's suitable to merge. I
> don't know who typically does that; I haven't involved myself in the GSoC
> projects before.
All righty. I'll check with wms and see if the server is setup already to
accept incoming reports.
smime.p7s
Description:
On Oct 5, 2011, at 20:45, Jeremy Lavergne wrote:
>> We do have a Google Summer of Code project in progress to deliver a
>> statistics interface about installed ports.
>
> It's actually completed...
Ah, I see.
> when will it get added to trunk?
When someone evaluates the work and determines i
> We do have a Google Summer of Code project in progress to deliver a
> statistics interface about installed ports.
It's actually completed... when will it get added to trunk?
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users m
On Oct 5, 2011, at 16:56, Scott Webster wrote:
> Do we keep track of requests to packages.macports.org to figure out
> which binaries are most important to add to the repository?
I have certainly never seen any web server statistics from MacPorts.
We do have a Google Summer of Code project in p
Do we keep track of requests to packages.macports.org to figure out
which binaries are most important to add to the repository?
Scott
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/mac
