Re: [vos-d] build system reviews (long)
Uh, I don't think giving everybody accounts on baikonur (the interreality.org server) is going to solve much. For one thing, it only runs Debian, and a big part of the discussion here is how best to support building on Windows and OS X. We intend to do 3rd party world hosting at some point in the future, but that will go on a separate box from interreality.org. I don't want to take the risk of a rogue script disrupting the box that handles our email, web page, mailing list, bzr repositories, etc. On Thu, Apr 26, 2007 at 01:02:08PM -0700, HEBLACK, J wrote: On Thu, 2007-04-26 at 09:21 -0400, Reed Hedges wrote: On Wed, Apr 25, 2007 at 11:07:11PM -0400, Peter Amstutz wrote: [1] Although there is a case to be made that such files should be included in your repository anyway, since there are people who might want to check out the latest source for something but still don't want to be required to have every last little build tool. Thoughts? Hello people, How about installing a sandbox or build sandbox at the main VOS station for devs to link scripts, Java, JavaScript, ..., whose scripts would not disturb Lead Programmers or VOS Architects. Thoughts? The official sandbox will have network constraint conditions saying that what is built officially is there for the VOS station only and not other networks? A sample devs account is like this: the first six letters from the devs last name followed by the first initial from the devs name; like this: [EMAIL PROTECTED] -- JASON A HEBLACK [EMAIL PROTECTED] APT 3 (650) 289 - 0954 450 EAST O'KEEFE EAST PALO ALTO, CA 94303 ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] signature.asc Description: Digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] build system reviews (long)
On Wed, Apr 25, 2007 at 11:07:11PM -0400, Peter Amstutz wrote: It's actually make distcheck that's interesting in this case. In automake it gives you a single command that will build a source tarball, unpack it to another directory, runs configure and does a build. It's a very useful automated sanity check on your source distribution. Also make dist is distinguished from simply dumping your repository to a tar file by the fact that it includes certain generated scripts like configure that don't, strictly speaking, belong in your version control branch (since they're automatically generated from other files.) In another project I've basically implemented this in a set of common Makefile rules. It is a bit annoying to debug complex make rules like this but it's not that hard my main problem is working in various odd policies and methods still around from a previous version of this stuff, and some of the nonstandard stuff we did there, VOS follows more normal conventions. [1] Although there is a case to be made that such files should be included in your repository anyway, since there are people who might want to check out the latest source for something but still don't want to be required to have every last little build tool. Thoughts? The problem with this is you can end up with these files being regerenerated all the time and end up with a zillion revisions, each with no significant change from the previous. Reed ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] build system reviews (long)
On Thu, 2007-04-26 at 09:21 -0400, Reed Hedges wrote: On Wed, Apr 25, 2007 at 11:07:11PM -0400, Peter Amstutz wrote: [1] Although there is a case to be made that such files should be included in your repository anyway, since there are people who might want to check out the latest source for something but still don't want to be required to have every last little build tool. Thoughts? Hello people, How about installing a sandbox or build sandbox at the main VOS station for devs to link scripts, Java, JavaScript, ..., whose scripts would not disturb Lead Programmers or VOS Architects. Thoughts? The official sandbox will have network constraint conditions saying that what is built officially is there for the VOS station only and not other networks? A sample devs account is like this: the first six letters from the devs last name followed by the first initial from the devs name; like this: [EMAIL PROTECTED] -- JASON A HEBLACK [EMAIL PROTECTED] APT 3 (650) 289 - 0954 450 EAST O'KEEFE EAST PALO ALTO, CA 94303 ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] build system reviews (long)
On Wed, 25 Apr 2007 23:07:11 -0400, Peter Amstutz wrote: It's actually make distcheck that's interesting in this case. Ok, but the first step to get there is to replicate make dist :-) Also make dist is distinguished from simply dumping your repository to a tar file by the fact that it includes certain generated scripts like configure that don't, strictly speaking, belong in your version control branch (since they're automatically generated from other files.) Yeah, I appreciate the complexity, but I'm still ok with doing it. By comparing with bzr export I didn't intend to mean it will be trivial, just that I have previous experience that should help me. best, Lalo Martins -- So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable. - personal:http://lalo.hystericalraisins.net/ technical:http://www.hystericalraisins.net/ GNU: never give up freedom http://www.gnu.org/ ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
