Robert P. J. Day wrote:
> On Fri, 29 Jul 2005, Thomas Beale wrote:
>
>
>>Apparently I have not explained myself sufficiently clearly...what I
>>am suggesting is that knowledge of the directories
>>trunk/tags/branches/release be built into the tools at the client
>>end. This would be done in such a way that they would no longer
>>appear in the 'normal' directory hierarchy but instead would (for
>>example) display the contents of those directories as views, or in
>>some other way.
>
>
> i understand what you're saying but how would you suggest this be
> done? not in terms of actual implementation, just in the abstract
> sense?
>
> first, i'm hoping that, by typing "view", you're not suggesting that
> this would require a GUI of some sort.
not literally no. What I meant was: imagine you did a checkout of a
repostory; imagine then that you had to do a set_view command to choose
trunk or some named branch of development, and that thereafter you were
in the normal directory structure, but corresponding to the chosen
version of development.
>
> having the trunk/tags/branches/etc. appear as normal directories might
> seem tacky to you, but it's a *very* simple way to support this. i
> get the feeling that, if you tried to make this more transparent, it
> would just get way more complicated for little gain.
>
> rday
Well it's not a case of being tacky, it's just that the directory system
is being used to simulate something which has nothing to do with
directories. It's not that it doesn't work at all, but it will cause
errors, and inconsistencies (e.g. in paths in build scripts).
- thomas beale
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 30 14:09:05 2005