[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Glen <glen.84_at_gmail.com>
Date: Thu, 14 Feb 2008 21:19:29 +0200

Hi Mark,

I received a reply regarding the lack of certificate authorities with
Subversion on Windows, and apparently this has changed in version 1.5
(it will try to use the Windows certificate store to verify
certificates). How soon after the final release of Subversion 1.5 do you
think Subclipse will support it?

Thanks,

Glen.

P.S. Shall I assume that my RFE below was rejected?

-------- Original Message --------
Subject: Re: [Subclipse-users] 2 suggestions and a question
Date: Wed, 30 Jan 2008 21:49:46 +0200
From: Glen <glen.84_at_gmail.com>
To: users_at_subclipse.tigris.org
References: <479624F3.4010801_at_gmail.com>
<ff892c5d0801221013n5ab9cb5fp65d4e188925f9b3a_at_mail.gmail.com>
<4796466C.3080601_at_gmail.com>
<ff892c5d0801301125w56c4cda7kcd0dcc83080d3545_at_mail.gmail.com>

Mark,

> The main issue was just that export does not create the main path, ...

I'm not sure what you mean here. What do you mean by 'main path'? Do you
mean it's not possible to specify the PATH of the export with the
available API?

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

Well like I said, the dynamic naming is not as important (although it
would help when exporting HEAD), as just being able to specify the name
of the directory where the export is saved (using the PATH). Don't you
ever find yourself wanting to include the revision in the name of the
export? ('Something 1.5.0.0') I realise it can be renamed afterwards,
but why, if SVN makes PATH available?

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

I hope so, because it looks silly chopped off. What use is 'SVN
Reposito...'?

Can this toolbar button be named differently to the item in the 'Open
Perspective' dialogue?

Thanks,

Glen.

Mark Phippard wrote:
> 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.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-02-14 20:19:49 CET

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.