This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Step-By-Step Build Instructions for MinGW gcc/gcj 3.4 Compilers
Besides the fully scripted "building" alternative, we could also create a "rsync"
possibility.
I was thinking of creating a special user on the machine I'm hosting, in whose home
folder a complete source + binaries deployment would be available for anybody to
rsync with(with the current cvs version).
I don't know if anybody would be interested? We could also do a thing like that from
the sourceforge infrastructure I guess.
The idea is that the three compilers (native linux, native cross-mingw, native
mingw) would be operational and kept up to date for who needs it, by just rsyncing
from the infrastructure servers.
No matter how well you explain the manual option, people will still balk at it. I
think it would be better to provide a "monolithical" script. People who complain,
because they like other options, already have the motivation to fix things. So, these
people won't balk at modifying a script. (The "options are evil"-strategy). If we
find that the same request comes back again and again, only then we should
carefully introduce an option along with a reasonable default (no options without
defaults!).
Anybody interested in helping out with this "easy deployment" strategy?