📄 copy.c
字号:
working and pristine propfiles over too. */
{
svn_node_kind_t kind;
const char *src_wprop, *src_bprop, *dst_wprop, *dst_bprop;
/* Discover the paths to the two text-base files */
const char *src_txtb = svn_wc__text_base_path (src_path, FALSE, pool);
const char *dst_txtb = svn_wc__text_base_path (dst_path, FALSE, pool);
/* Discover the paths to the four prop files */
SVN_ERR (svn_wc__prop_path (&src_wprop, src_path,
src_access, FALSE, pool));
SVN_ERR (svn_wc__prop_base_path (&src_bprop, src_path,
src_access, FALSE, pool));
SVN_ERR (svn_wc__prop_path (&dst_wprop, dst_path,
dst_parent, FALSE, pool));
SVN_ERR (svn_wc__prop_base_path (&dst_bprop, dst_path,
dst_parent, FALSE, pool));
/* Copy the text-base over unconditionally. */
SVN_ERR (svn_io_copy_file (src_txtb, dst_txtb, TRUE, pool));
/* Copy the props over if they exist. */
SVN_ERR (svn_io_check_path (src_wprop, &kind, pool));
if (kind == svn_node_file)
SVN_ERR (svn_io_copy_file (src_wprop, dst_wprop, TRUE, pool));
/* Copy the base-props over if they exist */
SVN_ERR (svn_io_check_path (src_bprop, &kind, pool));
if (kind == svn_node_file)
SVN_ERR (svn_io_copy_file (src_bprop, dst_bprop, TRUE, pool));
}
/* Schedule the new file for addition in its parent, WITH HISTORY. */
{
char *copyfrom_url;
svn_revnum_t copyfrom_rev;
SVN_ERR (svn_wc_get_ancestry (©from_url, ©from_rev,
src_path, src_access, pool));
/* Pass NULL, NULL for cancellation func and baton, as this is
only one file, not N files. */
SVN_ERR (svn_wc_add (dst_path, dst_parent,
copyfrom_url, copyfrom_rev,
NULL, NULL,
notify_copied, notify_baton, pool));
}
return SVN_NO_ERROR;
}
/* This function effectively creates and schedules a dir for
addition, but does extra administrative things to allow it to
function as a 'copy'.
ASSUMPTIONS:
- src_path points to a dir under version control
- dst_parent points to a dir under version control, in the same
working copy.
- dst_basename will be the 'new' name of the copied dir in dst_parent
*/
static svn_error_t *
copy_dir_administratively (const char *src_path,
svn_wc_adm_access_t *src_access,
svn_wc_adm_access_t *dst_parent,
const char *dst_basename,
svn_cancel_func_t cancel_func,
void *cancel_baton,
svn_wc_notify_func_t notify_copied,
void *notify_baton,
apr_pool_t *pool)
{
const svn_wc_entry_t *src_entry;
svn_wc_adm_access_t *adm_access;
/* The 'dst_path' is simply dst_parent/dst_basename */
const char *dst_path = svn_path_join (svn_wc_adm_access_path (dst_parent),
dst_basename, pool);
/* Sanity check: you cannot make a copy of something that's not
in the repository. See comment at the bottom of this file for an
explanation. */
SVN_ERR (svn_wc_entry (&src_entry, src_path, src_access, FALSE, pool));
if (! src_entry)
return svn_error_createf
(SVN_ERR_ENTRY_NOT_FOUND, NULL,
_("'%s' is not under version control"), src_path);
if ((src_entry->schedule == svn_wc_schedule_add)
|| (! src_entry->url)
|| (src_entry->copied))
return svn_error_createf
(SVN_ERR_UNSUPPORTED_FEATURE, NULL,
_("Cannot copy or move '%s': it is not in the repository yet; "
"try committing first"),
src_path);
/* Recursively copy the whole directory over. This gets us all
text-base, props, base-props, as well as entries, local mods,
schedulings, existences, etc.
### Should we be copying unversioned items within the directory? */
SVN_ERR (svn_io_copy_dir_recursively (src_path,
svn_wc_adm_access_path (dst_parent),
dst_basename,
TRUE,
cancel_func, cancel_baton,
pool));
/* If this is part of a move, the copied directory will be locked,
because the source directory was locked. Running cleanup will remove
the locks, even though this directory has not yet been added to the
parent. */
SVN_ERR (svn_wc_cleanup (dst_path, NULL, NULL, cancel_func, cancel_baton,
pool));
/* Remove all wcprops in the directory, because they're all bogus now.
After the commit, ra_dav should regenerate them and re-store them as
an optimization. Note we use the normal locking mechanism here, even
though this directory has not yet been added to the parent. */
SVN_ERR (svn_wc_adm_open2 (&adm_access, NULL, dst_path, TRUE, -1,
pool));
SVN_ERR (svn_wc__remove_wcprops (adm_access, TRUE, pool));
SVN_ERR (svn_wc_adm_close (adm_access));
/* Schedule the directory for addition in both its parent and itself
(this_dir) -- WITH HISTORY. This function should leave the
existing administrative dir untouched. */
{
char *copyfrom_url;
svn_revnum_t copyfrom_rev;
SVN_ERR (svn_wc_get_ancestry (©from_url, ©from_rev,
src_path, src_access, pool));
SVN_ERR (svn_wc_add (dst_path, dst_parent,
copyfrom_url, copyfrom_rev,
cancel_func, cancel_baton,
notify_copied, notify_baton, pool));
}
return SVN_NO_ERROR;
}
/* Public Interface */
svn_error_t *
svn_wc_copy (const char *src_path,
svn_wc_adm_access_t *dst_parent,
const char *dst_basename,
svn_cancel_func_t cancel_func,
void *cancel_baton,
svn_wc_notify_func_t notify_func,
void *notify_baton,
apr_pool_t *pool)
{
svn_wc_adm_access_t *adm_access;
svn_node_kind_t src_kind;
SVN_ERR (svn_wc_adm_probe_open2 (&adm_access, NULL, src_path, FALSE, -1,
pool));
SVN_ERR (svn_io_check_path (src_path, &src_kind, pool));
if (src_kind == svn_node_file)
SVN_ERR (copy_file_administratively (src_path, adm_access,
dst_parent, dst_basename,
notify_func, notify_baton, pool));
else if (src_kind == svn_node_dir)
SVN_ERR (copy_dir_administratively (src_path, adm_access,
dst_parent, dst_basename,
cancel_func, cancel_baton,
notify_func, notify_baton, pool));
SVN_ERR (svn_wc_adm_close (adm_access));
return SVN_NO_ERROR;
}
/*
Rabbinic Commentary
Q: Why can't we 'svn cp' something that we just copied?
i.e. 'svn cp foo foo2; svn cp foo2 foo3"
A: It leads to inconsistencies.
In the example above, foo2 has no associated repository URL,
because it hasn't been committed yet. But suppose foo3 simply
inherited foo's URL (i.e. foo3 'pointed' to foo as a copy
ancestor by virtue of transitivity.)
For one, this is not what the user would expect. That's
certainly not what the user typed! Second, suppose that the
user did a commit between the two 'svn cp' commands. Now foo3
really *would* point to foo2, but without that commit, it
pointed to foo. Ugly inconsistency, and the user has no idea
that foo3's ancestor would be different in each case.
And even if somehow we *could* make foo3 point to foo2 before
foo2 existed in the repository... what's to prevent a user from
committing foo3 first? That would break.
*/
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -