On Wed, Nov 18, 2009 at 04:52:04AM +1100, Peter Jeremy wrote:
It is the maintainer's responsibility to update the port. If the
existing maintainer has vanished, you can take over maintainership by
submitting a PR that updates the port and changes the MAINTAINER line.
If the ports team are
On Wed, Nov 18, 2009 at 2:19 AM, Scot Hetzel swhet...@gmail.com wrote:
On Tue, Nov 17, 2009 at 3:59 PM, Eitan Adler eitanadlerl...@gmail.com wrote:
Actually, I *had* a patch that got the source from svn, tarred it
and checksummed it, with little modification to the do-fetch target
and abusing
(Sorry, Ive lost track of the higher level attributions, but)
Eitan Adler wrote:
Creating deterministic tars (ignoring metadeta) sounds like it
should be a solved problem by now. If it isn't then I will have to
make it my next project ;)
Instead of creating tar files, create zip files and then
Status update.
I've now begun producing regular builds from GCC SVN for GCC, G++, GNAT
and fortran on 7.2 amd64. The build logs are published here:
http://gcc.coreland.ath.cx/
I'm hoping this will increase awareness of regressions before they make
their way back into releases (the formal GCC
On Wed, 18 Nov 2009 11:43:07 +, Thomas Sandford
freebsdu...@paradisegreen.co.uk wrote:
(Sorry, Ive lost track of the higher level attributions, but)
Eitan Adler wrote:
Creating deterministic tars (ignoring metadeta) sounds like it
should be a solved problem by now. If it isn't then I will
