[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Shoudn't this pristine thing be a version 1 issue?

From: Paul Lussier <pll_at_lanminds.com>
Date: 2003-03-11 21:53:28 CET

In a message dated: Tue, 11 Mar 2003 14:25:33 CST
Florin Iucha said:

>How about our company which has developers from Hamburg to Cincinnati
>to St. Paul to St. Diego to Bombay? All the developer sites have big
>honking Solaris machines.

*THIS* would be a good reason to have repo replication! :)

>> If you're users are all on PCs with Exceed, wouldn't it make more=20
>> sense for them to use something like SVN where they can check out the=20
>> code from the 'big Solaris/AIX/SGI servers' to their local disk, then=20
>> check in to merge with others? They must have gobs of spare disk=20
>> space on their local drives?
>
>How about compiling and debugging? We are not just editing text files.

Understood, but the editing could be done locally in a wc, when you
need to debug/compile, check it into a private branch, co that branch
on the 'big honking Solaris machine' and compile/debug.

You could even set up something relatively automated so that upon
check-in, the build process is kicked off and all the output is
mailed back to the developer. Then, when/if they need to debug, they
can log onto the 'big honking Solaris machine' and debug.

Of course, this is a 'pie-in-the-sky' theory. I am, by no means,
trying to tell you how to develop, or how your workflow should
structured. You know what works best given your environment, I'm
just saying 'you could do X' given the information I currently have :)
(IOW, there are a bazillion reasons why what I suggest might not work
in any given location !)

>> Did I miss something somewhere?
>
>It matters if they are 15 thin copies or 15 thick copies.
>
>The code for having a smart/fat worklocation can be ripped out. If you
>need source "near you", you can create a slave repository "near you".
>That might mean one slave per (development server group)/site.

Oh, I think I see what you're saying. I thought you were suggesting
having each developer clone the repo, then check out locally from
their private repo. But I get the sense now, that you're saying each
site would clone from a master, and that would reside on each sites
'big honking Solaris machine'. Each developer could then co from
that. Is that what you're saying?

If so, that makes perfect sense to me (well, right now anyway :)

Thanks for the clarification!

-- 
Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.
	 If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 11 21:54:15 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.