Indeed I use the trunc/branches/tags architecture for
new projects. But my need is more configuration. I
appreciate the powerfull "copy" fonction, but it
creates branches, so cannot be use for configuration
across the branches. I can't flag "i386" a whole
directory then "ppc" another (like it can be done
trough properties) and ask something like
svn checkout svn://host/proj/branches/v1.2 -flag ppc
to get only the directories/files flagged "ppc" (this
flag being associated to the directory independently
of the copies made (or versions)).
So my only solution is to specify a "view" ppc who
countains all the leaves files and checkout them
individually to get my ppc configuration
Thanks for your time Ryan, I had a way to do it now
even if it's costly.
--- Ryan Schmidt <subversion-2005@ryandesign.com> a
écrit :
> On Oct 20, 2005, at 12:06, jerome jansou wrote:
>
> > Thanks Ryan for your answer,
> >
> > I would like to process as you suggest, but It's
> hard.
> > I have many projects under the same svn
> repository,
> > and I ofen update the whole thing from top level,
> so
> > an update would re-create the deleted directory.
>
> It looks like you're not following the trunk /
> branches / tags model
> exactly... for those who do follow this model, and
> who release often,
> the tags directory gets quite full of copies of the
> project. Checking
> out the entire repository would therefore be a very
> space-consuming
> operation, not to mention a waste of time -- you
> never need to check
> out a tag, since you're never supposed to be
> modifying it. Therefore,
> most people don't check out the root of the
> repository; rather, they
> check out the trunk(s) of the project(s), and maybe
> the current branch
> (es).
>
>
> > Additionaly, I have subdirectories for different
> > architectures in each project sometimes 5 levels
> under
> > the project. I neither need then nor want them all
> > (because of a poor disk space concern, i concede,
> but
> > mainly because I do not want to deliver everything
> to
> > my final client).
> > So this CVS way of customising by hand the
> directories
> > I do not want to keep allow me to get a kind of
> > "clearcase" view (snapshot like of course).
> > The main idea is that it's easier to remove what I
> do
> > not want than making a full list of what I want
> and
> > checkout this list.
>
> Then you need "svn checkout -N". Unfortunately, it
> has never worked
> correctly, and it is inadvisable to use it.
>
>
http://subversion.tigris.org/issues/show_bug.cgi?id=695
>
> Someone is apparently currently working on some
> major enhancements in
> this area.
>
> http://svn.haxx.se/users/archive-2005-08/0255.shtml
>
>
> > How dangerous is it to edit this Entries file ?
> > Maybe I had to quit this addiction... ;-)
>
> I've not used any revision control system other than
> Subversion, so I
> do not have the same habits or assumptions you do,
> coming from CVS. I
> cannot say how dangerous it is to edit the files, I
> just know that
> Subversion intends to maintain them itself, and I'm
> content to let it
> do so. It knows what it's doing. I, as a
> counterexample, do not, and
> I would not want to jeopardize my working copy, and
> thereby my
> repository, by mucking with it.
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail:
> users-help@subversion.tigris.org
>
>
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 20 12:59:17 2005