Hi, Uli,
Von: Ulrich Eckhardt [mailto:ulrich.eckhardt_at_dominolaser.com]
> On Monday 22 August 2011, Markus Schaber wrote:
> > We need to add a new directory including files and properties to a
> > subversion repository "in-place".
>
> Just to be sure: There are auto-props, which could help in combination
> with an import. There is also svn_load_dirs, in case you need this for
> maintaining vendor branches.
Auto-props won't help us, as we save object specific metadata
(Decoration for the repo browser, device configurations etc.) in the
properties.
Svn_load_dirs won't help us either, as our "source" is the CoDeSys
internal project database, and not a directory tree.
> > With SVN 1.6, the following did work: (I know that this is only an
> > artifact and was no documented / intended behavior.)
> > - Checkout the parent directory to a temporary place.
> > - create and svn add the data directory under the parent working
copy.
> > - svn add and svn propset all the children we need in the working
copy.
> > - svn commit the parent directory (to add everything in a single
> > commit.)
> > - move the data directory to the intended working copy place.
> > - delete the temporary parent directory.
>
> Yes, there was some recent discussion whether to allow forking a child
> working copy from a parent working copy. If I remember correctly, this
is
> out of question for 1.7 and rather something for 1.8 or 1.9.
Forking the child tree would allow us to get rid of the second commit,
for the price of copying the data directory, instead of moving it. But
we could do the fork before populating all the subdirectories, so that
would be fast enough.
> > Is it theoretically possible with the new working copy architecture
to
> > allow the working copy root itself to be "scheduled for addition"?
> >
> > This could be the base for a nice feature for SVN 1.8, allowing both
> > "in-place import" and "import with properties", maybe some command
> > like "svn checkout --for-addition
> >
svn://destination/url/to/some/non/existing/directory/with/existing/paren
t".
>
> +1
>
> I never use import, because I always get the exact repository location
> wrong, either one too few or one too many directory levels. Having
> something import- like that creates a working copy would be a very
> interesting feature. It allows you to verify the target URL, set
> properties, exclude artifacts from builds or other version control
> systems, test stuff etc and do all that before committing.
>
> I'm not sure it is feasible with the current or new WC design though,
> because additions are typically operations on the parent directory.
I'm
> confident the SVN team will figure out a solution though.
I consider this impossible with SVN 1.6 working copy format, as we need
the parent directory to exist for its metadata. But in SVN 1.7, we have
a central metadata storage in the workingcopy root, so I think it should
be doable.
Best regards
Markus Schaber
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 |
Fax +49-831-54031-50
Email: m.schaber@3s-software.com | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects:
http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner |
Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
Received on 2011-08-22 17:09:11 CEST