Simon Large wrote:
> Molle Bestefich wrote:
> > Simon Large wrote:
> > > Molle Bestefich wrote:
> > > > Or just hack the entries file and remove the dir entry.
> > >
> > > If that is in the FAQ, tell me where and I will delete it
> > > straight away. You should _never_ hack the entries file.
> >
> > That's not what I said, at least it's not what I tried to say..
> > I'll try again:
> >
> > There's an entry in the FAQ which explains one way to get
> > non-modifiable shared files working. Basically, check out the shared
> > files separately, and then copy the checked-out WC into your project
> > WC. This will do weird things to Subversion, causing it to leave the
> > sub-WC alone.
>
> This is a nested WC, and it is standard subversion behaviour. Same
> effect as creating a new folder in your WC and checking out something
> else into it.
Fair enough.
I meant "weird" from a user's POV, not from a technical perspective.
As in "it's weird with that WC layout thing, under some circumstances
nested WC's are committed, under some they're not".
Really, it was a sidenote, and was only meant as yet another reason
why a better and more formal method should be introduced to support the
concept of shared files.
> > The same affect can be achieved by simply nuking the directory entry
> > for the sub-WC from the "entries" file. The advantage of doing it
> > this way is that the checkout operation is easier (and thus perhaps
> > easier to explain to your team).
>
> I think you are mixing up 2 different scenarios. That one was about a
> repository folder which contains (say) 10 folders, of which I am
> interested in 3.
I'm unsure what you mean by "that one"...
> If I check out the top level I get all 10 projects.
> There was talk about checking out the top level folder only and then
> hacking the entries file so that when you update you get only the 3
> projects you are interested in. But that is definitely not recommended
> by us. If you really want to be able to update all 3 projects together,
> creating a local project which pulls them in using svn:externals is a
> better way to go. Otherwise just check out the 3 projects individually.
... so I'm not sure what you mean by this.
But nevermind. Let's just drop this whole "hack the entries file"
discussion - it was after all just a non-relevant and minor sidenote
to the main discussion..
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu May 26 16:52:28 2005