Actually, can someone tell me what is going on with the DNS?
The folks at Addison-Wesley, who provide rubycentral.com, seem
to be having some “administrative issues”.
Dave’s been on them for over to week to get the problem resolved,
but it is apparently still a problem. But we really need a better home;
one with more bandwidth, mirroring, etc.
So I’m setting up an area on Sourceforge to distribute new releases
of the windows installer. As soon as this latest Fox issue
is resolved and I fix a couple of niggling bugs, I’ll put
fresh versions up and announce the URL’s.
Oh, and also my setup.exe builder for your own self-contained
applications (I announced this at RubyConf).
Author of “The Pragmatic Programmer” * “Programming Ruby” * The Agile Manifesto
Columnist for IEEE Software Magazine * Board of Directors, Agile Alliance
Pragmatic T-shirts available at: www.pragmaticprogrammer.com/merchandise.html
So I’m setting up an area on Sourceforge to distribute new releases
of the windows installer. As soon as this latest Fox issue
is resolved and I fix a couple of niggling bugs, I’ll put
fresh versions up and announce the URL’s.
Neat.
Oh, and also my setup.exe builder for your own self-contained
applications (I announced this at RubyConf).
Author of “The Pragmatic Programmer” * “Programming Ruby” * The Agile
Manifesto
Columnist for IEEE Software Magazine * Board of Directors, Agile Alliance
Pragmatic T-shirts available at: www.pragmaticprogrammer.com/merchandise.html
So I’m setting up an area on Sourceforge to distribute new releases
of the windows installer. As soon as this latest Fox issue
is resolved and I fix a couple of niggling bugs, I’ll put
fresh versions up and announce the URL’s.
What Fox issue? I’m using FXRuby-1.0.15 and fox-1.0.26 on linux and
windows, and the dangling ptr problem is history.
>Actually, can someone tell me what is going on with the DNS?
The folks at Addison-Wesley, who provide rubycentral.com, seem
to be having some “administrative issues”.
That’s an awfully polite way of saying “haven’t got a clue” …
Dave’s been on them for over to week to get the problem resolved,
but it is apparently still a problem.
Tell them to transfer the domain to their register.com account already.
The problem has to do with the fact that this domain is still under
Network Solutions and for some reason the rubycentral.com domain isn’t
properly in the root name server for the .COM TLD … or at least, A.GTLD-SERVERS.NET doesn’t know who the NS are for the domain …
I guess someone could always try and send email to NSTLD@VERISIGN-GRS.com and complain about the breakage of rubycentral.com and see if they can do something about it. But, moving
the domain over to Pearson’s Register.com will force an update to the
root servers and probably correct the problem, anyway.
But we really need a better home; one with more bandwidth, mirroring,
etc.
Is bandwidth really a problem? Shouldn’t be … mirroring would be
nice, though.
–
Dossy Shiobara mail: dossy@panoptic.com
Panoptic Computer Network web: http://www.panoptic.com/
“He realized the fastest way to change is to laugh at your own
folly – then you can let go and quickly move on.” (p. 70)
Something I brought up, which may not be an issue…Lyle is looking into
it.
-rich
···
-----Original Message-----
From: Joel VanderWerf [mailto:vjoel@PATH.Berkeley.EDU]
Sent: Wednesday, November 13, 2002 5:04 PM
To: ruby-talk ML
Subject: Re: Where is RubyCentral?
Andrew Hunt wrote:
…
So I’m setting up an area on Sourceforge to distribute new
releases of
the windows installer. As soon as this latest Fox issue is
resolved
and I fix a couple of niggling bugs, I’ll put fresh versions up and
announce the URL’s.
What Fox issue? I’m using FXRuby-1.0.15 and fox-1.0.26 on linux and
windows, and the dangling ptr problem is history.
What Fox issue? I’m using FXRuby-1.0.15 and fox-1.0.26 on linux and
windows, and the dangling ptr problem is history.
Yes, it’s unrelated to the dangling pointer problem that you were seeing.
There was a subtle (but unintended) change in the semantics for how
stuff from the Fox module gets “included” when you do:
include Fox
I haven’t had a chance to digest exactly what’s going on, but after I’ve
done so I’ll try to summarize somewhere. It’s not really what I’d call a
bug, and I’m not sure that there’s anything to “fix” yet; but the
problem is that most or all of the FreeRIDE code was written to depend
on the previous semantics and as a result is now broken.
I’m not trying to be vague I just don’t quite have a handle on what
has changed (or why this change had the effect that it did).
