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

Re: Advice on code sharing

From: Chris Velevitch <chris.velevitch_at_gmail.com>
Date: Wed, 21 Jan 2009 11:03:00 +1100

I don't know which version of the documentation you been reading (I
have svnbook for v1.5 r3305) and whilst I haven't used externals, from
reading the book, it seems that you can specify, in the external,
which revision gets checkout when someone checks out or updates their
working copy. That way no one gets any nasty surprises when the share
is being updated. And then once the changes to the share has been
finalised, you then update the external, which is also versioned. So
the next time someone updates their working copy they get the new
share.

However, your continuous integration scripts for both packages will
need to always get the latest revision to ensure changes that break
the other package get noticed as early as possible.

Chris

--
Chris Velevitch
Manager - Adobe Platform Users Group, Sydney
m: 0415 469 095
www.apugs.org.au
Adobe Platform Users Group, Sydney
Feb '09 meeting: TBA
Date: Mon 23rd Feb January 6pm for 6:30 start
Details and RSVP coming soon
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1039779
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-21 01:03:57 CET

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

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