Re: svn usage tips

2010-03-02 Thread David Weintraub 
On Tue, Mar 2, 2010 at 2:31 PM, Paul Decker  wrote:
> I am talking about checking out a single project, however the "projects" all
> use the same folders, like shared folders.  So when you do a get on the top
> level, you get all the files for every project rather than just the files
> for the project of interest
>

What does your repository directory structure look like? I don't need
a detailed picture. Just an overview.

It sounds like you're saying that the structure looks like this:

/project1
/project2
/project3
/common1
/common2
/common3
/common4


If you are working on /project1, you need to checkout folders
/common1, /common2, /common3, /common4 too.

If that's the case, you'll need to use --depth:

$ # Checks out the root project, but no folders
$ svn co --depth=empty svn://subversion/ workspace-project1
$ cd workspace-project1

$ #Now we have to "update" the missing folders
$ svn update --set-depth=infinity project1 common1 common2 common3 common4

This will checkout your project, and the needed shared folders. When
you do an update, it won't "update" the missing stuff.

A better way is to use "externals". Take a look at
. This
is the way shared folders are suppose to be used. That way, you can
set the version of the shared folder with the project. For example, it
is possible that the latest version of the shared folder might not be
compatible with the version of the project.

This way, you can checkout project1 and all the common folders will
automatically be checkout too.

-- 
David Weintraub
qazw...@gmail.com

Re: svn usage tips

2010-03-02 Thread Mark Keisler 
So are all of these projects in the same repository?  That's what I was
assuming.

-- 
Mark
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."


On Tue, Mar 2, 2010 at 2:21 PM, Bob Archer  wrote:

>  Why not set up your projects so they only include the needed shared
> folders using externals?
>
>
>
> BOb
>
>
>
>
>
> *From:* Paul Decker [mailto:kg...@comcast.net]
> *Sent:* Tuesday, March 02, 2010 2:31 PM
> *To:* David Weintraub
>
> *Cc:* users@subversion.apache.org
> *Subject:* Re: svn usage tips
>
>
>
> I am talking about checking out a single project, however the "projects"
> all use the same folders, like shared folders.  So when you do a get on the
> top level, you get all the files for every project rather than just the
> files for the project of interest
>
>
>
> - Original Message -
> From: "David Weintraub" 
> To: "Paul Decker" 
> Cc: users@subversion.apache.org
> Sent: Tuesday, March 2, 2010 2:08:55 PM GMT -05:00 US/Canada Eastern
> Subject: Re: svn usage tips
>
> Let me get this straight, you're not talking about checking out a single
> project vs. the whole tree. You're talking about checking out a project, but
> not the externals directories? You can take a look at several things: *
> There's an --ignore-externals flag when you do a checkout. This prevents any
> externals directory from being checked out. * Take a look at the --depth
> switch. You can checkout a directory, without checking out the
> sub-directories, then just update the subdirectories you want. (Note:
> There's a --set-depth flag on the update command to override the setting on
> the checkout command. (See
> http://subversion.apache.org/docs/release-notes/1.5.html#sparse-checkoutsfor 
> more information on the depth switch.) On Tue, Mar 2, 2010 at 1:07 PM,
> Paul Decker wrote: > Hi list, > > > > I recently changed jobs and went from
> a cvs house to a svn house.   They > have many projects and have an
> extensive shared source base.   I would like > to know if there is a way to
> setup to check out a list of folders or > files.   In other words, for each
> project, I want to check out only files > that are directly related to that
> project rather than evey file which is in > the shared directory. > > > >
> ie. > > > > projects\ > > \display > > \display2 > > \display3 > > \comm > >
> \usb > > \tcp > > \keyboard > > \spi > > \i2c > > \flash > > \eeprom > > > >
> Some projects use {display, comm, keyboard, spi } while other projects use >
> {display, usb, spi, flash }   currently, the only way of working is to check
> > out all folders. > > > > Is there a better way to work? > > > > thanks, >
> > Paul > > -- David Weintraub qazw...@gmail.com
> Let me get this straight, you're not talking about checking out a single
> project vs. the whole tree. You're talking about checking out a project, but
> not the externals directories? You can take a look at several things: *
> There's an --ignore-externals flag when you do a checkout. This prevents any
> externals directory from being checked out. * Take a look at the --depth
> switch. You can checkout a directory, without checking out the
> sub-directories, then just update the subdirectories you want. (Note:
> There's a --set-depth flag on the update command to override the setting on
> the checkout command. (See
> http://subversion.apache.org/docs/release-notes/1.5.html#sparse-checkoutsfor 
> more information on the depth switch.) On Tue, Mar 2, 2010 at 1:07 PM,
> Paul Decker wrote: > Hi list, > > > > I recently changed jobs and went from
> a cvs house to a svn house.   They > have many projects and have an
> extensive shared source base.   I would like > to know if there is a way to
> setup to check out a list of folders or > files.   In other words, for each
> project, I want to check out only files > that are directly related to that
> project rather than evey file which is in > the shared directory. > > > >
> ie. > > > > projects\ > > \display > > \display2 > > \display3 > > \comm > >
> \usb > > \tcp > > \keyboard > > \spi > > \i2c > > \flash > > \eeprom > > > >
> Some projects use {display, comm, keyboard, spi } while other projects use >
> {display, usb, spi, flash }   currently, the only way of working is to check
> > out all folders. > > > > Is there a better way to work? > > > > thanks, >
> > Paul > > -- David Weintraub qazw...@gmail.com
>

RE: svn usage tips

2010-03-02 Thread Bob Archer 
Why not set up your projects so they only include the needed shared folders 
using externals?

BOb


From: Paul Decker [mailto:kg...@comcast.net]
Sent: Tuesday, March 02, 2010 2:31 PM
To: David Weintraub
Cc: users@subversion.apache.org
Subject: Re: svn usage tips

I am talking about checking out a single project, however the "projects" all 
use the same folders, like shared folders.  So when you do a get on the top 
level, you get all the files for every project rather than just the files for 
the project of interest



- Original Message -
From: "David Weintraub" 
To: "Paul Decker" 
Cc: users@subversion.apache.org
Sent: Tuesday, March 2, 2010 2:08:55 PM GMT -05:00 US/Canada Eastern
Subject: Re: svn usage tips

Let me get this straight, you're not talking about checking out a single 
project vs. the whole tree. You're talking about checking out a project, but 
not the externals directories? You can take a look at several things: * There's 
an --ignore-externals flag when you do a checkout. This prevents any externals 
directory from being checked out. * Take a look at the --depth switch. You can 
checkout a directory, without checking out the sub-directories, then just 
update the subdirectories you want. (Note: There's a --set-depth flag on the 
update command to override the setting on the checkout command. (See 
http://subversion.apache.org/docs/release-notes/1.5.html#sparse-checkouts for 
more information on the depth switch.) On Tue, Mar 2, 2010 at 1:07 PM, Paul 
Decker wrote: > Hi list, > > > > I recently changed jobs and went from a cvs 
house to a svn house.   They > have many projects and have an extensive shared 
source base.   I would like > to know if there is a way to setup to check out a 
list of folders or > files.   In other words, for each project, I want to check 
out only files > that are directly related to that project rather than evey 
file which is in > the shared directory. > > > > ie. > > > > projects\ > > 
\display > > \display2 > > \display3 > > \comm > > \usb > > \tcp > > \keyboard 
> > \spi > > \i2c > > \flash > > \eeprom > > > > Some projects use {display, 
comm, keyboard, spi } while other projects use > {display, usb, spi, flash }   
currently, the only way of working is to check > out all folders. > > > > Is 
there a better way to work? > > > > thanks, > > Paul > > -- David Weintraub 
qazw...@gmail.com
Let me get this straight, you're not talking about checking out a single 
project vs. the whole tree. You're talking about checking out a project, but 
not the externals directories? You can take a look at several things: * There's 
an --ignore-externals flag when you do a checkout. This prevents any externals 
directory from being checked out. * Take a look at the --depth switch. You can 
checkout a directory, without checking out the sub-directories, then just 
update the subdirectories you want. (Note: There's a --set-depth flag on the 
update command to override the setting on the checkout command. (See 
http://subversion.apache.org/docs/release-notes/1.5.html#sparse-checkouts for 
more information on the depth switch.) On Tue, Mar 2, 2010 at 1:07 PM, Paul 
Decker wrote: > Hi list, > > > > I recently changed jobs and went from a cvs 
house to a svn house.   They > have many projects and have an extensive shared 
source base.   I would like > to know if there is a way to setup to check out a 
list of folders or > files.   In other words, for each project, I want to check 
out only files > that are directly related to that project rather than evey 
file which is in > the shared directory. > > > > ie. > > > > projects\ > > 
\display > > \display2 > > \display3 > > \comm > > \usb > > \tcp > > \keyboard 
> > \spi > > \i2c > > \flash > > \eeprom > > > > Some projects use {display, 
comm, keyboard, spi } while other projects use > {display, usb, spi, flash }   
currently, the only way of working is to check > out all folders. > > > > Is 
there a better way to work? > > > > thanks, > > Paul > > -- David Weintraub 
qazw...@gmail.com

Re: svn usage tips

2010-03-02 Thread Paul Decker 
I am talking about checking out a single project, however the "projects" all 
use the same folders, like shared folders.  So when you do a get on the top 
level, you get all the files for every project rather than just the files for 
the project of interest 



- Original Message - 
From: "David Weintraub"  
To: "Paul Decker"  
Cc: users@subversion.apache.org 
Sent: Tuesday, March 2, 2010 2:08:55 PM GMT -05:00 US/Canada Eastern 
Subject: Re: svn usage tips 

Let me get this straight, you're not talking about checking out a single 
project vs. the whole tree. You're talking about checking out a project, but 
not the externals directories? You can take a look at several things: * There's 
an --ignore-externals flag when you do a checkout. This prevents any externals 
directory from being checked out. * Take a look at the --depth switch. You can 
checkout a directory, without checking out the sub-directories, then just 
update the subdirectories you want. (Note: There's a --set-depth flag on the 
update command to override the setting on the checkout command. (See 
http://subversion.apache.org/docs/release-notes/1.5.html#sparse-checkouts for 
more information on the depth switch.) On Tue, Mar 2, 2010 at 1:07 PM, Paul 
Decker wrote: > Hi list, > > > > I recently changed jobs and went from a cvs 
house to a svn house.   They > have many projects and have an extensive shared 
source base.   I would like > to know if there is a way to setup to check out a 
list of folders or > files.   In other words, for each project, I want to check 
out only files > that are directly related to that project rather than evey 
file which is in > the shared directory. > > > > ie. > > > > projects\ > > 
\display > > \display2 > > \display3 > > \comm > > \usb > > \tcp > > \keyboard 
> > \spi > > \i2c > > \flash > > \eeprom > > > > Some projects use {display, 
comm, keyboard, spi } while other projects use > {display, usb, spi, flash }   
currently, the only way of working is to check > out all folders. > > > > Is 
there a better way to work? > > > > thanks, > > Paul > > -- David Weintraub 
qazw...@gmail.com 
Let me get this straight, you're not talking about checking out a single 
project vs. the whole tree. You're talking about checking out a project, but 
not the externals directories? You can take a look at several things: * There's 
an --ignore-externals flag when you do a checkout. This prevents any externals 
directory from being checked out. * Take a look at the --depth switch. You can 
checkout a directory, without checking out the sub-directories, then just 
update the subdirectories you want. (Note: There's a --set-depth flag on the 
update command to override the setting on the checkout command. (See 
http://subversion.apache.org/docs/release-notes/1.5.html#sparse-checkouts for 
more information on the depth switch.) On Tue, Mar 2, 2010 at 1:07 PM, Paul 
Decker wrote: > Hi list, > > > > I recently changed jobs and went from a cvs 
house to a svn house.   They > have many projects and have an extensive shared 
source base.   I would like > to know if there is a way to setup to check out a 
list of folders or > files.   In other words, for each project, I want to check 
out only files > that are directly related to that project rather than evey 
file which is in > the shared directory. > > > > ie. > > > > projects\ > > 
\display > > \display2 > > \display3 > > \comm > > \usb > > \tcp > > \keyboard 
> > \spi > > \i2c > > \flash > > \eeprom > > > > Some projects use {display, 
comm, keyboard, spi } while other projects use > {display, usb, spi, flash }   
currently, the only way of working is to check > out all folders. > > > > Is 
there a better way to work? > > > > thanks, > > Paul > > -- David Weintraub 
qazw...@gmail.com

Re: svn usage tips

2010-03-02 Thread David Weintraub 
Let me get this straight, you're not talking about checking out a
single project vs. the whole tree. You're talking about checking out a
project, but not the externals directories?

You can take a look at several things:

* There's an --ignore-externals flag when you do a checkout. This
prevents any externals directory from being checked out.

* Take a look at the --depth switch. You can checkout a directory,
without checking out the sub-directories, then just update the
subdirectories you want. (Note: There's a --set-depth flag on the
update command to override the setting on the checkout command.

(See http://subversion.apache.org/docs/release-notes/1.5.html#sparse-checkouts
for more information on the depth switch.)

On Tue, Mar 2, 2010 at 1:07 PM, Paul Decker  wrote:
> Hi list,
>
>
>
> I recently changed jobs and went from a cvs house to a svn house.   They
> have many projects and have an extensive shared source base.   I would like
> to know if there is a way to setup to check out a list of folders or
> files.   In other words, for each project, I want to check out only files
> that are directly related to that project rather than evey file which is in
> the shared directory.
>
>
>
> ie.
>
>
>
> projects\
>
> \display
>
> \display2
>
> \display3
>
> \comm
>
> \usb
>
> \tcp
>
> \keyboard
>
> \spi
>
> \i2c
>
> \flash
>
> \eeprom
>
>
>
> Some projects use {display, comm, keyboard, spi } while other projects use
> {display, usb, spi, flash }   currently, the only way of working is to check
> out all folders.
>
>
>
> Is there a better way to work?
>
>
>
> thanks,
>
> Paul
>
>



-- 
David Weintraub
qazw...@gmail.com

Re: svn usage tips

2010-03-02 Thread Mark Keisler 
On Tue, Mar 2, 2010 at 12:07 PM, Paul Decker  wrote:

> Hi list,
>
>
>
> I recently changed jobs and went from a cvs house to a svn house.   They
> have many projects and have an extensive shared source base.   I would like
> to know if there is a way to setup to check out a list of folders or
> files.   In other words, for each project, I want to check out only files
> that are directly related to that project rather than evey file which is in
> the shared directory.
>
>
>
> ie.
>
>
>
> projects\
>
> \display
>
> \display2
>
> \display3
>
> \comm
>
> \usb
>
> \tcp
>
> \keyboard
>
> \spi
>
> \i2c
>
> \flash
>
> \eeprom
>
>
>
> Some projects use {display, comm, keyboard, spi } while other projects use
> {display, usb, spi, flash }   currently, the only way of working is to check
> out all folders.
>
>
>
> Is there a better way to work?
>
>
>
> thanks,
>
> Paul
>
>
>
See  http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html