headers
Matthias Odisio | 22 May 2008 15:35
Picon

co-existing CVS and Subversion

Hi,

I have a directory that is managed both by CVS (with a remote server) and 
by Subversion (with a local repository). Yes, it's not ideal at all, but 
that's the setup.

The CVS menu of BBedit is restricted to only Update, Commit, Show status, 
Export project and Show log, as if BBedit were thniking the files are not 
managed by CVS. If I try to update, I'm asked for a CVSROOT, whereas the 
CVS/Root file is pointing to the remote server.

What is going wrong?

Nota Bene:
The Subversion menu of BBedit is working fine.
When I use the command line clients (cvs, svn), everything behaves 
correctly.

Matthias

--

-- 
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <support <at> barebones.com>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to:  <bbedit-talk-off <at> barebones.com>
Permalink | Reply |
headers
Jim Correia | 23 May 2008 02:07

Re: co-existing CVS and Subversion

On May 22, 2008, at 9:35 AM, Matthias Odisio wrote:

> I have a directory that is managed both by CVS (with a remote  
> server) and by Subversion (with a local repository). Yes, it's not  
> ideal at all, but that's the setup.
>
> The CVS menu of BBedit is restricted to only Update, Commit, Show  
> status, Export project and Show log, as if BBedit were thniking the  
> files are not managed by CVS. If I try to update, I'm asked for a  
> CVSROOT, whereas the CVS/Root file is pointing to the remote server.
>
> What is going wrong?

As currently structured, BBEdit assumes that a given directory will  
only be used with on SCM system.

I've logged a feature request so I can relax this restriction/ 
assumption in the future.

Jim

--

-- 
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <support <at> barebones.com>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to:  <bbedit-talk-off <at> barebones.com>
(Continue reading)

Permalink | Reply |
headers
Timothy Stone | 23 May 2008 02:21
Favicon

Re: co-existing CVS and Subversion


On May 22, 2008, at 8:07 PM, Jim Correia wrote:

> On May 22, 2008, at 9:35 AM, Matthias Odisio wrote:
>
>> I have a directory that is managed both by CVS (with a remote  
>> server) and by Subversion (with a local repository). Yes, it's not  
>> ideal at all, but that's the setup.
>>
>> The CVS menu of BBedit is restricted to only Update, Commit, Show  
>> status, Export project and Show log, as if BBedit were thniking the  
>> files are not managed by CVS. If I try to update, I'm asked for a  
>> CVSROOT, whereas the CVS/Root file is pointing to the remote server.
>>
>> What is going wrong?
>
> As currently structured, BBEdit assumes that a given directory will  
> only be used with on SCM system.
>
> I've logged a feature request so I can relax this restriction/ 
> assumption in the future.
>

I'm not sure, if I was BB, that I would even consider this... reason:  
the setup described above, and in the original post, is "not ideal at  
all," but not at all what CVS or SVN, or PVCS, or /insert SCM here/  
expects. Nor, is it any documented, or recommended project management  
pattern.

To Matthias, I would ask, "Why are you being constrained to one
(Continue reading)

Permalink | Reply |
headers
Charles Albrecht | 23 May 2008 05:17
Picon
Favicon

Re: co-existing CVS and Subversion


On May 22, 2008, at 5:21 PM, Timothy Stone wrote:
>
> I'm not sure, if I was BB, that I would even consider this...  
> reason: the setup described above, and in the original post, is  
> "not ideal at all," but not at all what CVS or SVN, or PVCS, or / 
> insert SCM here/ expects. Nor, is it any documented, or recommended  
> project management pattern.
>
> To Matthias, I would ask, "Why are you being constrained to one  
> directory?" What is preventing you from have a "work" directory,  
> under which there is a "svn/project_name" and "cvs/project_name"  
> directory? It is an automated build process? What sort of project  
> would want you to use two different SCM repositories.
>
> This is something I do on a daily basis, and if there is something  
> that I can assist with, I only need to know more about what you are  
> doing to provide some direction.
>

The usage pattern for this is the private versioning pattern (ref  
http://www.scmpatterns.com/book/pattern-summary.html) in which you  
essentially version all of your local "off-code-line" work  
independently from the source codeline. This sounds like what  
Matthias is looking to implement. It allows, essentially micro- 
versioning of your work in progress with a local repository that.  
Other approaches for this involve creating honest-to-god branches in  
the host source control system and submitting all your changes there,  
but multiple branches can be even more problematic from a keeping-up- 
to-date-with-the-donor-branch than the orthogonal version control
(Continue reading)

Permalink | Reply |
headers
Timothy Stone | 23 May 2008 12:13
Favicon

Re: co-existing CVS and Subversion


On May 22, 2008, at 11:17 PM, Charles Albrecht wrote:

>
> On May 22, 2008, at 5:21 PM, Timothy Stone wrote:
>>
>> I'm not sure, if I was BB, that I would even consider this...  
>> reason: the setup described above, and in the original post, is  
>> "not ideal at all," but not at all what CVS or SVN, or PVCS, or / 
>> insert SCM here/ expects. Nor, is it any documented, or recommended  
>> project management pattern.
>>
>> To Matthias, I would ask, "Why are you being constrained to one  
>> directory?" What is preventing you from have a "work" directory,  
>> under which there is a "svn/project_name" and "cvs/project_name"  
>> directory? It is an automated build process? What sort of project  
>> would want you to use two different SCM repositories.
>>
>> This is something I do on a daily basis, and if there is something  
>> that I can assist with, I only need to know more about what you are  
>> doing to provide some direction.
>>
>
> The usage pattern for this is the private versioning pattern (ref
http://www.scmpatterns.com/book/pattern-summary.html) 
>  in which you essentially version all of your local "off-code-line"  
> work independently from the source codeline. This sounds like what  
> Matthias is looking to implement.

I'm not sure that Matthias is describing a "pattern," but a problem.
(Continue reading)

Permalink | Reply |
headers
Matthias Odisio | 23 May 2008 16:44
Picon

Re: co-existing CVS and Subversion

Thanks a lot for your sounded responses!

On Fri, 23 May 2008, Timothy Stone wrote:

>>> I'm not sure, if I was BB, that I would even consider this... 
>>> reason: the setup described above, and in the original post, is 
>>> "not ideal at all," but not at all what CVS or SVN, or PVCS, or / 
>>> insert SCM here/ expects. Nor, is it any documented, or recommended 
>>> project management pattern.
>>>
>>> To Matthias, I would ask, "Why are you being constrained to one 
>>> directory?" What is preventing you from have a "work" directory, 
>>> under which there is a "svn/project_name" and "cvs/project_name" 
>>> directory? It is an automated build process? What sort of project 
>>> would want you to use two different SCM repositories.
>>>
>>> This is something I do on a daily basis, and if there is something 
>>> that I can assist with, I only need to know more about what you are 
>>> doing to provide some direction.
>>>
>>
>> The usage pattern for this is the private versioning pattern (ref 
> http://www.scmpatterns.com/book/pattern-summary.html)
>>  in which you essentially version all of your local "off-code-line" 
>> work independently from the source codeline. This sounds like what 
>> Matthias is looking to implement.

Yes, this is what I'm trying to do.

> I'm not sure that Matthias is describing a "pattern," but a problem.
(Continue reading)

Permalink | Reply |
headers
Gabor Maghera | 22 May 2008 19:18
Picon
Gravatar

Re: co-existing CVS and Subversion

Did you happen to change your OS username or user directory for the
system you are working on?  I had the same issue and it turned out
that BBEdit had an incorrect path in one of the preferences.

Cheers,
Gabor

On 5/22/08, Matthias Odisio <modisio <at> gmail.com> wrote:
> Hi,
>
> I have a directory that is managed both by CVS (with a remote server) and
> by Subversion (with a local repository). Yes, it's not ideal at all, but
> that's the setup.
>
> The CVS menu of BBedit is restricted to only Update, Commit, Show status,
> Export project and Show log, as if BBedit were thniking the files are not
> managed by CVS. If I try to update, I'm asked for a CVSROOT, whereas the
> CVS/Root file is pointing to the remote server.
>
> What is going wrong?
>
> Nota Bene:
> The Subversion menu of BBedit is working fine.
> When I use the command line clients (cvs, svn), everything behaves
> correctly.
>
> Matthias
>
> --
> ------------------------------------------------------------------
(Continue reading)

Permalink | Reply |
headers
Matthias Odisio | 22 May 2008 22:14
Picon

Re: co-existing CVS and Subversion

On Thu, 22 May 2008, Gabor Maghera wrote:

> Did you happen to change your OS username or user directory for the
> system you are working on?  I had the same issue and it turned out
> that BBEdit had an incorrect path in one of the preferences.
>
> Cheers,
> Gabor
>

No, I've not made such changes. I've looked in my BBedit preferences and 
they looked fine.

Matthias

>
>
> On 5/22/08, Matthias Odisio <modisio <at> gmail.com> wrote:
>> Hi,
>>
>> I have a directory that is managed both by CVS (with a remote server) and
>> by Subversion (with a local repository). Yes, it's not ideal at all, but
>> that's the setup.
>>
>> The CVS menu of BBedit is restricted to only Update, Commit, Show status,
>> Export project and Show log, as if BBedit were thniking the files are not
>> managed by CVS. If I try to update, I'm asked for a CVSROOT, whereas the
>> CVS/Root file is pointing to the remote server.
>>
>> What is going wrong?
(Continue reading)

Permalink | Reply |
headers
Charles Albrecht | 22 May 2008 20:48
Picon
Favicon

Re: co-existing CVS and Subversion

Matthias,

Keep in mind that BBEdit and the shell use different environment  
variables, so if you need $CVSROOT or $CVS_RSH, you may need to set  
them in the environment.plist. I haven't tried setting bbedit's scm  
parameters, because I've never quite understood how they're supposed  
to work.

Still, it seems that CVS/Root should have the CVSROOT value after the  
initial checkout.

-Charles
  charlesa <at> pobox.com

On May 22, 2008, at 10:18 AM, "Gabor Maghera" <gmaghera <at> gmail.com>  
wrote:

> Did you happen to change your OS username or user directory for the
> system you are working on?  I had the same issue and it turned out
> that BBEdit had an incorrect path in one of the preferences.
>
> Cheers,
> Gabor
>
>
>
> On 5/22/08, Matthias Odisio <modisio <at> gmail.com> wrote:
>> Hi,
>>
>> I have a directory that is managed both by CVS (with a remote
(Continue reading)

Permalink | Reply |

Gmane