Gonzalo Tornaria wrote: > On Wed, Oct 14, 2009 at 7:12 AM, Dr. David Kirkby > <david.kir...@onetel.net> wrote: >> 2) When submitting a patch, they attach logs showing building on all >> platforms, *except* the one they normally work on, since one can assume >> they have probably got their patch working there. > > I don't think this would work at all, unless there is an *easy* > automated procedure to submit a patch to a bot which (a) applies the > patch to the current tree (b) compiles in all platforms (c) attaches > the logs to the ticket and possibly flags the ticket depending on the > result of the test.
A build bot would be nice, but I do not myself see the fact it is not dead easy to test on another platform, and have a build bot automatically attach a patch, should be an excuse for not checking. I certainly check my patches on hardware other than what I develop it on. > OTOH, maybe if binary distributions for "t2" were readily available > (as they are (?) for sage.math), that would encourage some people to > actually try some patches in solaris. There is a binary which is pretty old. I'll try to get a later one up. > <rant> > BTW, logging into T2 and getting errors in my .bashrc already > discourages me to get anywhere near solaris. Just one small sample: > > grep: illegal option -- q > Usage: grep -hblcnsviw pattern file . . . > > Can you please check for me whether "grep -q" is posix or not? > </rant> > > Gonzalo That one is very easy to fix. the -q option to grep just causes it to be quite, and give no output. You can achieve exactly the same effect by simply redirecting the output of the grep command to /dev/null. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
