svn propedit with vc?

svn propedit with vc?

[joakim]

Would it be possible to support "svn propedit" with vc? 

-- 
Joakim Verona

Re: svn propedit with vc?

[Dan Nicolaescu]

joakim@verona.se writes:

> Would it be possible to support "svn propedit" with vc? 

What exactly would you want to do?
(I am familiar with VC, so I could help with that, but not familiar with "svn propedit" at all...)

Re: svn propedit with vc?

[joakim]

Dan Nicolaescu <dann@gnu.org> writes:

> joakim@verona.se writes:
>
>> Would it be possible to support "svn propedit" with vc? 
>
> What exactly would you want to do?
> (I am familiar with VC, so I could help with that, but not familiar with "svn propedit" at all...)

Svn supports meta-information for files and directories. These can have
all sorts of semantics, or user-defined.

Basically a property behaves like a special type of file, or a commit
message. I'm not proficient enough with VC to know exactly how it would
fit in the existing infrastructure. I suppose many other SCM:s just
store meta-data as plain files, like .gitignore or whatever. 

My concrete use-case is editing the svn:externals property, which is
described here:

http://svnbook.red-bean.com/en/1.0/ch07s03.html

So, I do svn propedit svn:external ., and emacs pops up due to
EDITOR=emacsclient. However, this isnt convenient when on a remote host,
so I imagined VC could take care of this case remotely, just as with
files. 


Heres the help message for propedit:

,----
| [joakim@localhost ith]$ svn --help propedit
| propedit (pedit, pe): Edit a property with an external editor.
| usage: 1. propedit PROPNAME TARGET...
|        2. propedit PROPNAME --revprop -r REV [TARGET]
| 
|   1. Edits versioned prop in working copy or repository.
|   2. Edits unversioned remote prop on repos revision.
|      TARGET only determines which repository to access.
| 
| See 'svn help propset' for more on setting properties.
| 
| Valid options:
|   -r [--revision] ARG      : ARG (some commands also take ARG1:ARG2 range)
|                              A revision argument can be one of:
|                                 NUMBER       revision number
|                                 '{' DATE '}' revision at start of the date
|                                 'HEAD'       latest in repository
|                                 'BASE'       base rev of item's working copy
|                                 'COMMITTED'  last commit at or before BASE
|                                 'PREV'       revision just before COMMITTED
|   --revprop                : operate on a revision property (use with -r)
|   -m [--message] ARG       : specify log message ARG
|   -F [--file] ARG          : read log message from file ARG
|   --force-log              : force validity of log message source
|   --editor-cmd ARG         : use ARG as external editor
|   --encoding ARG           : treat value as being in charset encoding ARG
|   --with-revprop ARG       : set revision property ARG in new revision
|                              using the name[=value] format
|   --force                  : force operation to run
| 
| Global options:
|   --username ARG           : specify a username ARG
|   --password ARG           : specify a password ARG
|   --no-auth-cache          : do not cache authentication tokens
|   --non-interactive        : do no interactive prompting
|   --trust-server-cert      : accept unknown SSL server certificates without
|                              prompting (but only with '--non-interactive')
|   --config-dir ARG         : read user configuration files from directory ARG
|   --config-option ARG      : set user configuration option in the format:
|                                  FILE:SECTION:OPTION=[VALUE]
|                              For example:
|                                  servers:global:http-library=serf
| 
`----

-- 
Joakim Verona

Re: svn propedit with vc?

[Dan Nicolaescu]

joakim@verona.se writes:

> Dan Nicolaescu <dann@gnu.org> writes:
>
>> joakim@verona.se writes:
>>
>>> Would it be possible to support "svn propedit" with vc? 
>>
>> What exactly would you want to do?
>> (I am familiar with VC, so I could help with that, but not familiar with "svn propedit" at all...)
>
> Svn supports meta-information for files and directories. These can have
> all sorts of semantics, or user-defined.
>
> Basically a property behaves like a special type of file, or a commit
> message. I'm not proficient enough with VC to know exactly how it would
> fit in the existing infrastructure. I suppose many other SCM:s just
> store meta-data as plain files, like .gitignore or whatever. 
>
> My concrete use-case is editing the svn:externals property, which is
> described here:
>
> http://svnbook.red-bean.com/en/1.0/ch07s03.html
>
> So, I do svn propedit svn:external ., and emacs pops up due to
> EDITOR=emacsclient. However, this isnt convenient when on a remote host,
> so I imagined VC could take care of this case remotely, just as with
> files. 

Hard to say if this is what you want: it looks like psvn.el has some
code to deal with properties.  Similar code could be added to
vc-svn.el and some menu entries could be added to Tools / VC 
and vc-dir (for svn managed files/directories)