You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Hacksaw <dt...@irobot.com> on 2009/09/29 20:18:04 UTC
Enhancement to ^/ syntax
The ^/ syntax is pretty cool, but still doesn't really replace the $CVSROOT
functionality, since that is useful when checking out a folder.
My suggestion is to have aliases definable in the config file, or in an
environement variable. These would then be used in the same sort of syntax:
---Config---
[aliases]
jbx svn+ssh://svn/svn/JumboBox
fish svn://example.com/svn/guppie++
---gifnoC---
Then the syntax could be
svn co ^jbx/trunk/src
And so on.
What do folks think? Has this been discussed?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401766
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Enhancement to ^/ syntax
Posted by Hacksaw <dt...@irobot.com>.
On 9/29/09 17:20 , "Bob Archer" <Bo...@amsi.com> wrote:
>> On Sep 29, 2009, at 4:18 PM, Hacksaw wrote:
>>
>>> The ^/ syntax is pretty cool, but still doesn't really replace the
>>> $CVSROOT
>>> functionality, since that is useful when checking out a folder.
>>>
>>> My suggestion is to have aliases definable in the config file, or in
>>> an
>>> environement variable. These would then be used in the same sort of
>>> syntax:
>>>
>>>
>>> ---Config---
>>>
>>> [aliases]
>>> jbx svn+ssh://svn/svn/JumboBox
>>> fish svn://example.com/svn/guppie++
>>>
>>> Then the syntax could be
>>>
>>> svn co ^jbx/trunk/src
>>>
>>> And so on.
>>>
>>> What do folks think? Has this been discussed?
>>
>> I'm just wondering why this belongs in Subversion proper. How does
>> this differ from just using environment variables set in a .bashrc (or
>> similar platform-specific location)?
>
> I'm not even sure what the big advantage of this is. Once you do your checkout
> svn knows the path to the repository and you don't really need to use it a lot
> from that point on. You can use WC paths and the tab key in your shell to help
> with long paths.
>
> BOb
>
So, I have a collection of repo's at my company, on the order of forty or
so. It's never "once you do your check out", it's "oh, I need the bleeding
edge of that package, and this other package, and how did so and so solve
this problem again?"
It's also different in that it could conceivably be more than just the root,
it could just be a simple string substitution alias, which means that a URL
like
svn+ssh://apollo.astronauts.example.com/svn/quaternionlib/trunk/feynman/src
Could be ^qfeyn/.
Not using the shell syntax means it's screamingly obvious this is a
subverion construction, increasing the readability of any shell code that
might involve such thing, and limiting where one would go to look for the
list of aliases. Shell variables can be assigned and munged in too many
places.
Andy Levy asks:
>What happens if the user doesn't have the alias you're using defined
>in their config or environment? Especially in the case of hook
>scripts, but also regular users?
The same thing that happens anytime you hand svn a broken URL.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402119
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: Enhancement to ^/ syntax
Posted by Bob Archer <bo...@amsi.com>.
> On Sep 29, 2009, at 4:18 PM, Hacksaw wrote:
>
> > The ^/ syntax is pretty cool, but still doesn't really replace the
> > $CVSROOT
> > functionality, since that is useful when checking out a folder.
> >
> > My suggestion is to have aliases definable in the config file, or in
> > an
> > environement variable. These would then be used in the same sort of
> > syntax:
> >
> >
> > ---Config---
> >
> > [aliases]
> > jbx svn+ssh://svn/svn/JumboBox
> > fish svn://example.com/svn/guppie++
> >
> > Then the syntax could be
> >
> > svn co ^jbx/trunk/src
> >
> > And so on.
> >
> > What do folks think? Has this been discussed?
>
> I'm just wondering why this belongs in Subversion proper. How does
> this differ from just using environment variables set in a .bashrc (or
> similar platform-specific location)?
I'm not even sure what the big advantage of this is. Once you do your checkout svn knows the path to the repository and you don't really need to use it a lot from that point on. You can use WC paths and the tab key in your shell to help with long paths.
BOb
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401788
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Enhancement to ^/ syntax
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Hyrum K. Wright wrote on Tue, 29 Sep 2009 at 16:38 -0400:
> On Sep 29, 2009, at 4:18 PM, Hacksaw wrote:
> > ---Config---
> >
> > [aliases]
> > jbx svn+ssh://svn/svn/JumboBox
> > fish svn://example.com/svn/guppie++
> >
> >
> > ---gifnoC---
> >
> >
> >
> > Then the syntax could be
> >
> > svn co ^jbx/trunk/src
>
I like the general idea.
> I'm just wondering why this belongs in Subversion proper. How does
> this differ from just using environment variables set in a .bashrc (or
> similar platform-specific location)?
>
You can use them from any client? (without GUIs having to implement
$FOO parsing of their textboxes)
The client can list them? (By iterating the config hash)
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2403084
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Enhancement to ^/ syntax
Posted by "Hyrum K. Wright" <hy...@hyrumwright.org>.
On Sep 29, 2009, at 4:18 PM, Hacksaw wrote:
> The ^/ syntax is pretty cool, but still doesn't really replace the
> $CVSROOT
> functionality, since that is useful when checking out a folder.
>
> My suggestion is to have aliases definable in the config file, or in
> an
> environement variable. These would then be used in the same sort of
> syntax:
>
>
> ---Config---
>
> [aliases]
> jbx svn+ssh://svn/svn/JumboBox
> fish svn://example.com/svn/guppie++
>
>
> ---gifnoC---
>
>
>
> Then the syntax could be
>
> svn co ^jbx/trunk/src
>
> And so on.
>
> What do folks think? Has this been discussed?
I'm just wondering why this belongs in Subversion proper. How does
this differ from just using environment variables set in a .bashrc (or
similar platform-specific location)?
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401773
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Enhancement to ^/ syntax
Posted by Andy Levy <an...@gmail.com>.
On Tue, Sep 29, 2009 at 16:18, Hacksaw <dt...@irobot.com> wrote:
> The ^/ syntax is pretty cool, but still doesn't really replace the $CVSROOT
> functionality, since that is useful when checking out a folder.
>
> My suggestion is to have aliases definable in the config file, or in an
> environement variable. These would then be used in the same sort of syntax:
>
>
> ---Config---
>
> [aliases]
> jbx svn+ssh://svn/svn/JumboBox
> fish svn://example.com/svn/guppie++
>
>
> ---gifnoC---
>
>
>
> Then the syntax could be
>
> svn co ^jbx/trunk/src
>
> And so on.
>
> What do folks think? Has this been discussed?
What happens if the user doesn't have the alias you're using defined
in their config or environment? Especially in the case of hook
scripts, but also regular users?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401771
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].