svn:externals for Timeline code?

Hey Hiran, Mignon, and anyone else who might have advice on
this,

I've been thinking about the new SIMILE Timeline code that
we just added 
to the "third_party" directory in our SVN
repository.  Right now, the 
Timeline code in our SVN repository is a copy of the code
from the 
SIMILE project SVN repository.  Alternatively, we could add
an 
"svn:externals" property to our
"third_party" directory, to include the 
Timeline code "by reference" instead of
"by copy".  (More info about 
svn:externals here: http:
//svnbook.red-bean.com/en/1.0/ch07s03.html )

We're already using an "svn:externals" property
setting to include the 
dojo source tree in our OpenRecord "third_party"
directory.  Using 
"svn:externals" has the advantages that, (a) it
makes it really easy to 
periodically upgrade to the current version of the
third-party code, and 
(b) it discourages us (prevents us) from making any
modifications to the 
code in the third-party directory.  The disadvantage is that
it creates 
a dependency on the SVN server of the third-party project. 
There isn't 
much practical downside to OpenRecord having a dependency on
the SVN 
repository of the Dojo Toolkit, since both the Dojo Toolkit
SVN 
repository and OpenRecord SVN repository are on the same
server, 
administered by the same person.  But is it a mistake to
introduce a 
dependency on the SIMILE SVN server, which could be
intermittently down, 
or might someday move to a new address (or go away)?

I'm inclined to use the "svn:externals"
property for the SIMILE Timeline 
code instead of having a copy in our repository, but I feel
like I'm 
just guessing about this, and I was hoping somebody else
might have 
advice to offer.

Also, is there a better name for the
"third_party" directory?  I figure 
this sort of directory must be common in software projects
-- anybody 
know of a standard name for it?

 Brian






____________________________________________________________
_______
Copyright rights relinquished. This work is in the Public
Domain.
For details see: htt
p://creativecommons.org/licenses/publicdomain/

openrecord-dev mailing list
openrecord-devlists.berlios.de
https://lists.berlios.de/mailman/listinfo/openrecord-dev

I would think using the svn external would be a good thing. 
Since you 
can specify the revision that you want checkout, its just
quite nice  
  However, I had difficulties on some occasions.  I think
you can only 
have one extern in any particular directory, so we'll need
to test that 
or see if there is some directory structure that eliminates
this 
wierdness.  I could of course just be misinterpreting the
information 
i've read about it...the docs on externals seems to be
somewhat lacking 
to me, but thats how it goes.

Dustin


Brian Douglas Skinner wrote:
> Hey Hiran, Mignon, and anyone else who might have
advice on this,
> 
> I've been thinking about the new SIMILE Timeline code
that we just added 
> to the "third_party" directory in our SVN
repository.  Right now, the 
> Timeline code in our SVN repository is a copy of the
code from the 
> SIMILE project SVN repository.  Alternatively, we could
add an 
> "svn:externals" property to our
"third_party" directory, to include the 
> Timeline code "by reference" instead of
"by copy".  (More info about 
> svn:externals here: http:
//svnbook.red-bean.com/en/1.0/ch07s03.html )
> 
> We're already using an "svn:externals"
property setting to include the 
> dojo source tree in our OpenRecord
"third_party" directory.  Using 
> "svn:externals" has the advantages that,
(a) it makes it really easy to 
> periodically upgrade to the current version of the
third-party code, and 
> (b) it discourages us (prevents us) from making any
modifications to the 
> code in the third-party directory.  The disadvantage is
that it creates 
> a dependency on the SVN server of the third-party
project.  There isn't 
> much practical downside to OpenRecord having a
dependency on the SVN 
> repository of the Dojo Toolkit, since both the Dojo
Toolkit SVN 
> repository and OpenRecord SVN repository are on the
same server, 
> administered by the same person.  But is it a mistake
to introduce a 
> dependency on the SIMILE SVN server, which could be
intermittently down, 
> or might someday move to a new address (or go away)?
> 
> I'm inclined to use the "svn:externals"
property for the SIMILE Timeline 
> code instead of having a copy in our repository, but I
feel like I'm 
> just guessing about this, and I was hoping somebody
else might have 
> advice to offer.
> 
> Also, is there a better name for the
"third_party" directory?  I figure 
> this sort of directory must be common in software
projects -- anybody 
> know of a standard name for it?
> 
> 
Brian
> 
> 
> 
> 
> 
> 
> 
____________________________________________________________
_______
Copyright rights relinquished. This work is in the Public
Domain.
For details see: htt
p://creativecommons.org/licenses/publicdomain/

openrecord-dev mailing list
openrecord-devlists.berlios.de
https://lists.berlios.de/mailman/listinfo/openrecord-dev

Very thoughtful post. Question (reflecting ignorance of
svn): does an 
external reference imply that doing an svn update on your
repository 
will cause an update from the third party repository
automatically?
Thanks
Jack

Brian Douglas Skinner wrote:
> Hey Hiran, Mignon, and anyone else who might have
advice on this,
> 
> I've been thinking about the new SIMILE Timeline code
that we just added 
> to the "third_party" directory in our SVN
repository.  Right now, the 
> Timeline code in our SVN repository is a copy of the
code from the 
> SIMILE project SVN repository.  Alternatively, we could
add an 
> "svn:externals" property to our
"third_party" directory, to include the 
> Timeline code "by reference" instead of
"by copy".  (More info about 
> svn:externals here: http:
//svnbook.red-bean.com/en/1.0/ch07s03.html )
> 
> We're already using an "svn:externals"
property setting to include the 
> dojo source tree in our OpenRecord
"third_party" directory.  Using 
> "svn:externals" has the advantages that,
(a) it makes it really easy to 
> periodically upgrade to the current version of the
third-party code, and 
> (b) it discourages us (prevents us) from making any
modifications to the 
> code in the third-party directory.  The disadvantage is
that it creates 
> a dependency on the SVN server of the third-party
project.  There isn't 
> much practical downside to OpenRecord having a
dependency on the SVN 
> repository of the Dojo Toolkit, since both the Dojo
Toolkit SVN 
> repository and OpenRecord SVN repository are on the
same server, 
> administered by the same person.  But is it a mistake
to introduce a 
> dependency on the SIMILE SVN server, which could be
intermittently down, 
> or might someday move to a new address (or go away)?
> 
> I'm inclined to use the "svn:externals"
property for the SIMILE Timeline 
> code instead of having a copy in our repository, but I
feel like I'm 
> just guessing about this, and I was hoping somebody
else might have 
> advice to offer.
> 
> Also, is there a better name for the
"third_party" directory?  I figure 
> this sort of directory must be common in software
projects -- anybody 
> know of a standard name for it?
> 
> 
Brian
> 
____________________________________________________________
_______
Copyright rights relinquished. This work is in the Public
Domain.
For details see: htt
p://creativecommons.org/licenses/publicdomain/

openrecord-dev mailing list
openrecord-devlists.berlios.de
https://lists.berlios.de/mailman/listinfo/openrecord-dev

Dustin Machi wrote:
> I think you can only have one extern in any particular
directory,
> so we'll need to test that or see if there is some
directory 
> structure that eliminates this wierdness.  I could of
course 
> just be misinterpreting the information i've read
about it...

I think maybe you can only have one svn:externals *property*
in a 
particular directory, but I think the value of the
svn:externals 
property can include a newline-separated list of different
external 
modules.

 Brian



____________________________________________________________
_______
Copyright rights relinquished. This work is in the Public
Domain.
For details see: htt
p://creativecommons.org/licenses/publicdomain/

openrecord-dev mailing list
openrecord-devlists.berlios.de
https://lists.berlios.de/mailman/listinfo/openrecord-dev

Ok 

Brian Douglas Skinner wrote:
> Dustin Machi wrote:
>> I think you can only have one extern in any
particular directory,
>> so we'll need to test that or see if there is some
directory structure 
>> that eliminates this wierdness.  I could of course
just be 
>> misinterpreting the information i've read about
it...
> 
> I think maybe you can only have one svn:externals
*property* in a 
> particular directory, but I think the value of the
svn:externals 
> property can include a newline-separated list of
different external 
> modules.
> 
> 
Brian
> 
> 
> 
> 
____________________________________________________________
_______
Copyright rights relinquished. This work is in the Public
Domain.
For details see: htt
p://creativecommons.org/licenses/publicdomain/

openrecord-dev mailing list
openrecord-devlists.berlios.de
https://lists.berlios.de/mailman/listinfo/openrecord-dev

Jack Park wrote:
> Question (reflecting ignorance of svn): 
> does an external reference imply that doing an svn
update 
> on your repository will cause an update from the third 
> party repository automatically?

Yup, that's right.

 Brian


____________________________________________________________
_______
Copyright rights relinquished. This work is in the Public
Domain.
For details see: htt
p://creativecommons.org/licenses/publicdomain/

openrecord-dev mailing list
openrecord-devlists.berlios.de
https://lists.berlios.de/mailman/listinfo/openrecord-dev