Re: [Subclipse-users] 2 suggestions and a question

On Jan 22, 2008 2:39 PM, Glen <glen.84_at_gmail.com> wrote:
> > Can you expand on this with more details?
>
> Sure.
>
> If I export https://svn.cakephp.org/repo/branches/1.2.x.x to
> D:/Programming/PHP/Libraries/CakePHP, the command executed is:
>
> export -r HEAD https://svn.cakephp.org/repo/branches/1.2.x.x
> D:/Programming/PHP/Libraries/CakePHP/1.2.x.x
>
> As you can see, the last component of the URL (1.2.x.x) is appended to
> the local directory name. I would like to be able to specify a different
> name for the export, so that the command executed would be as follows:
>
> export -r HEAD https://svn.cakephp.org/repo/branches/1.2.x.x
> D:/Programming/PHP/Libraries/CakePHP/1.2.0.6402
>
> (Two notes: [1] '-r HEAD' is unnecessary [?] [2] It may be more logical
> to change the current working directory and then execute the export
> command, so that the full export path is not required [if that's possible])

HEAD is assumed, but it does not hurt. We do not really execute
commands anyway. The console is all just pseudo-logging.

We cannot manipulate CWD. That is not an option. We have to use full
local paths everywhere. Again, it is all kind of irrelevant for the
user anyway.

> So, the export window would ask for:
>
> Export directory: The directory to work from.
> Export path: The path within the directory to export to, for example
> '1.2.0.6402'. This could be left empty to use the default -- no path
> results in an export to: CWD/{last component of URL = 1.2.x.x in this
> case}. See http://svnbook.red-bean.com/en/1.1/re10.html

The main issue was just that export does not create the main path, so
we have to intuit what the user wants to do. We made the decision to
do it the way we did. I think we got it from TortoiseSVN.

> It would also be nice (but not as important), to be able to specify the
> path as: '1.2.0.$rev', for example, and to have the following command
> executed:
>
> export https://svn.cakephp.org/repo/branches/1.2.x.x
> 1.2.0.{revision being exported}
>
> (extra spaces above for clarity)
>
> Full example:
>
> Export directory: D:/Programming/PHP/Libraries/CakePHP
> Export path: 1.2.0.6402 (or 1.2.0.$rev)
>
> Resulting command, executed from 'D:/Programming/PHP/Libraries/CakePHP':
>
> export https://svn.cakephp.org/repo/branches/1.2.x.x 1.2.0.6402
>
> Hope this makes sense.

It doesn't seem very much like what we are shooting for with
Subclipse, especially the $rev part. That is what the command line is
for.

> > This name is based on the CVS plug-in using the name CVS Repository
> Exploring for their plug-in.
>
> Is that a 'no'? :-) ... :-(

More of an explanation. It is hard to know what the right thing to do
is. We might change it eventually.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org