On Jul 27, 2:39 pm, Stefan Küng <tortoise..._at_gmail.com> wrote:
> On 27.07.2009 20:22, steve wrote:
> Really, externals should be *really* external. If you have that many
> file externals, then you have not done a good job with capsuling your
> objects.
> Try creating a library for your many many files that are used in other
> projects and then include that library folder with an external.
>
I'm not sure why you think externals should only be pointing to
*really* external things as opposed to pointing to things that are (or
are intended to be) reusable things. In hardware, the better
designers will tend to create reusable cores that, on their own, may
not necessarily represent an entire chip design. The chip design will
be a collection of such cores. Those cores then are usable across
several different, unrelated designs.
OK, so you could arbitraily lump all of the cores, whether they are
related or not, into some library...and then at some point you'll
still want to reference multiple libraries. The spec'ed hardware
interfaces for the cores generally are good encapsulation, the lumping
together just to make it easier to use svn is not helping the
design...in fact it makes it harder in siutations sucha as one where
you want to hand off some cores to some outside place to use but don't
want to give away the whole lib.
>
> Seriously: if you use externals, either point them to a tag or use the
> '-r XXX' param in the external property.
>
When the cores are still under development along with the overall
design neither of those two options really works out well
- "point them to a tag": The issue is creating the tag in the first
place from something that uses externals into something that
explicitly references specific revisions but without having to do it
manually which is prone to error.
- "use the '-r XXX' param": When a widget is still under development,
having the user of the widget have to specify the particular revision
is potentially error prone...and prevents one from validating that
what is checked into 'head' is correct.
What we're trying to do is to create a tag with locked down external
references, from something that has externals that are not locked down
to specific revisions...but to do so without having to do it manually
and without having to lock down to specific revisions in the trunk.
Much like how VSS allows you to create labels. You can at any time
pull out an entire set of files and folders that represent the state
of the archive at the time that the label was created.
I don't see this as a Tortoise issue though, it's a Subversion one
that svncopy.pl attempts to provide a solution for...now if I could
just get svncopy.pl to do what it claims to do, I'd be a happy camper.
KJ
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2376195
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-28 08:12:20 CEST