Re: How to update a sparse directory?

Hi Mark,

Thank you for your reply.
Please see my comments below.

On Fri, Jun 07, 2019 at 03:37 PM PDT, Mark Phippard wrote:
> > On Jun 7, 2019, at 4:34 PM, Mun Johl <mun.johl_at_kazan-networks.com<mailto:mun.johl_at_kazan-networks.com>> wrote:
> >
> > We're using SVN version 1.8.19 on Red Hat Enterprise Linux 6.8 .
> >
> > For one of our projects, the SVN area is a sparse directory. I'm
> > wondering what's the best way to update that directory?
> >
> > I've searched the web but haven't found a definitive answer to how to
> > _update_ a sparse directory.
> >
> > Should I do an "svn update" at the root directory, and then traverse the
> > lower levels and do updates as well?
> >
> > Based on a web answer, I thought "svn update *" at the root level would
> > work; but it turns out that it doesn't actually update all directories
> > (at least, not in my case).
>
> You just run svn up and it basically says as much in the docs:
>
> http://svnbook.red-bean.com/en/1.7/svn.advanced.sparsedirs.html
>
> "Fortunately, having a complex collection of ambient depths in a single working copy doesn't complicate the way you interact with that working copy. You can still make, revert, display, and commit local modifications in your working copy without providing any new options (including --depth and --set-depth) to the relevant subcommands. Even svn update works as it does elsewhere when no specific depth is provided--it updates the working copy targets that are present while honoring their sticky depths."

I did see/read that, but "svn up" doesn't work for me.

> If this is not working for you provide a script that shows what you are doing and what you are getting.

If I do an "svn up" at the root dir, I get something like this:

Updating '.':
At revision 100000.

But I know that there have been updates down a few directory levels.
Hmm, I wonder if I'm not doing the "svn checkout" correctly. For
example:

If I'm in the dir "myDir" and I checkout sparsely as shown below:

   svn checkout svn://server.domain.com/abcd/branch_name/project1/one_dir project1/one_dir

Note that "project1" has other directories other than "one_dir", but for
the given project, only "one_dir" is required.

If I cd to myDir and enter "svn up", I get the output as shown above.
That is:

Updating '.':
At revision 100000.

If I cd to myDir/project1 and enter "svn up", I get the following
output:

svn: E155010: The node '.../myDir/project1' was not found.

where: ... is replacing the actual path.

And finally, if I cd to myDir/project1/one_dir and enter "svn up",
the directory structure is actually updated.

When I posted the original message I was hoping to find a command I can
enter at the root level (myDir) that would update the sparse
directories. But maybe I just need to traverse to where the actual
checkout is done (e.g. "one_dir") and do the update? Opinions?

If so, I can always create a script to make that easier for people
working on the respective project (more than one dir will require an
update).

Regards,

-- 
Mun