On Wed, Jun 10, 2009 at 6:11 AM, Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se
> wrote:
>
> I agree. The suggestion looks very nice to improve the usability of sparse
> checkouts, but the question is if it would be worth the work...
>
Well the question of whether it is worth the work or not doesn't
really come down to if the feature would be practical or not, it
basically comes down to who we can get to work on it. However, I think
both facts intertwine to some degree.
> I tend to consider reorganising my repository when I find myself in a
> situation where I would like to exclude some parts of a working copy. With a
> good repository layout, the need to use sparse checkouts can be almost
> completely eliminated.
>
You're wrong. There is no single definition for a "good repository
layout". It is highly subjective
and use-case
specific. Only the project or company can determine what the right
repository layout is for their needs, and that particular layout may
not be useful to other people. I've seen cases where externals
were the most useful path, and other cases where sparse directory support
were required and frequently used.
Determining if this feature is worth the effort is going to be nearly
impossible for these reasons.
A good example of what I'm talking about is a repository that must consider
multiple projects that share a single common code base, for example, an
engine of some sort. Normally the most ideal solution to this kind of
structure is to use externals (This was required in pre-svn 1.5 days) or
sparse checkouts. Without using these features, you would be required to
"duplicate" the "engine" in the repository itself, which is undesirable.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2360924
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-10 15:35:18 CEST