Re: discrepancies between 'svn -R list' and 'svn -R propget' (on windows using TSVN build command line client)
Bert Huijben wrote: >> -Original Message- >> From: Lorenz [mailto:loren...@yahoo.com] >> Sent: woensdag 16 november 2016 15:02 >> To: users@subversion.apache.org >> Subject: Re: discrepancies between 'svn -R list' and 'svn -R propget' (on >> windows using TSVN build command line client) >>[...] >> but what about the leading subpath vs. no subpath difference? >> >> svn -R ls path/subpath >> >> file1 >> subsubpath/file2 >> ... > >I don't think this was designed behavior... But it follows from the previous >answer: we just return the items relative from the url that you listed. >There is no easy way to do this differently as local paths might not match >remote paths, like when you have switched paths. > >So when we would show 'path/subpath/subsubpath/file2', it might be a >completely different result than the local relative path with the same name. > >> >> vs. >> >> svn -R pg svn:keywords path/subpath >> >> subpath/file1 - ... >> subpath/subsubpath/file2 >> ... > >And in this case we try to return the paths exactly in the form that you >used on the commandline, to allow you to match the result of multiple >arguments with multiple locations. >(Internally we convert to the absolute path and then back on output these >days, but we used to process everything in the original form before >Subversion 1.7) > >If you don't pass something like @rev or -r REV (or a URL instead of a >path), this will always match your local files. > > >Note that in both cases we recommend using --xml if you are going to parse >the output via tools as that has a more stable output format in case we add >new features in new releases. after some more experimenting it looks to me that: 'svn list' always returns paths relative to the given folder, independent if its given as a local path or as an URL. That even makes sense 8-) because it's always the repositry contents that is listed (as 'svn help list' tells in the first sentence) That also means 'svn list' won't show locally added files, but still list locally deleted files. 'svn propget' on the other hand returns paths relative to the CWD in case of a local path, or in case of an URL the complete URL. And it's showing local information in case of a local path, but repository information in case of an URL. I think 'svn help propget/list' should make that clear. All in all, there goes my idea of how to determine files missing certain properties. I'll open a new thread for that then. -- Lorenz
how to determine files missing certain propertiers?
Hi all, I'm trying to find files missing certain properties either locally in a WC, or remotely in a repository. I've experimented with scripting 'svn list' and 'svn propget' but that didn't work out because of my missunderstanding of what this commands really do (see threads "discrepancies between 'svn -R list' and 'svn -R propget'" and "svn --recursive and externals"). So, anyone out there with solutions/hints/links? -- Lorenz
Re: svn --recursive and externals
On Thu, Nov 17, 2016 at 07:54:04AM +, Lorenz wrote: > 'svn help pg' on the other hand doen't gives not infomation about > externals at all, and it rejects '--include-externals'. > So no recursing into externals with 'svn propget' at all 8-( Yes, propset/propget/proplist are a bit tricky. For example, what would happen if --include-externals was combined with the --revprop option? Keep in mind that SVN requires: "Must specify the revision as a number, a date or 'HEAD' when operating on a revision property" So what should happen if the user asks for a revprop recursively, and there are several repositories (with distinct revision number spaces) to query? What if -r NUMBER was also given? What if -r HEAD was given? Should the --include-externals and --revprop options be entirely mutually exclusive? That's one (of possibly) many questions that need to be asked before implementing such behaviour. It takes time to come up with a good design that interacts well with other existing command options. Recursing into externals is non-trivial to implement and has not been done everywhere. In scripts, you can work around this by finding all externals with 'svn status' first, and then calling propget on each.
SVNControl Documentation
Hello! Good afternoon! Is it possible for you provide me the documentation, guide or tutorial in order to integrate the tool "SVNCONTROL"?, and so I can manage subversion repositories in hosted Oracle Linux 7 from a computer with Windows. _PS: SVNControl is a system that allows to control the permissions and access to different repositories of Subversion. This tool requires Java installed to be able to run._ Thanks for your help, José!
Re: SVNControl Documentation
> On Nov 17, 2016, at 12:08 PM, s...@crccoding.com wrote: > > Hello! Good afternoon! > > Is it possible for you provide me the documentation, guide or tutorial in > order to integrate the tool "SVNControl"?, and so I can manage subversion > repositories in hosted Oracle Linux 7 from a computer with Windows. > > PS: SVNControl is a system that allows to control the permissions and access > to different repositories of Subversion. This tool requires Java installed > to be able to run. > > Thanks for your help, José! I've never heard of SVNControl. It looks like a separate project; here's how you can contact people who know about it: http://svncontrol.tigris.org/ds/viewForums.do
