Re: changing CVSROOT
Jens Miltner <[email protected]> Tue, 30 Mar 2004 22:22:07 +0200
| Newsgroups | gmane.comp.version-control.cvs.gui.devel |
|---|---|
| Message-ID | <[email protected]> |
Am 30.03.2004 um 22:38 schrieb Jerzy Kaczorowski:
> Jens,
>
>> (I just wanted to know whether major changes are on the way
>> before tackling this problem in MacCvs...)
>
> To make a long story short CVSROOT will simpy disappear from
> settings/preferences. There is no point in storing and managing it. We
> shall
> leave that to CVS(NT) itself.
>
> We will have the CVSROOT parameter for commands that may require it -
> checkout, login, rtag etc. It will be just a string added to the
> command
> using the -d parameter instead of returning the CVSROOT environmental
> variable in glue_getenv. CVSROOT wizard will help to format the
> string, but
> the user can also enter it all manually - very handy if you follow the
> instruction from some website on how to access their CVS repository.
>
> This will make all the problems disappear and our code will be simpler.
> Thanks to the new CVSROOT wizard we no londer have to code models of
> each
> protocol.
That sounds good so far, but we currently don't [yet?] have cvsnt on
Mac OS, so please keep in mind that the wizard may not work there...
I'd at least keep a popup of user defined CVSROOTs for that case, but
maybe that's something to be implemented in MacCvs only if it doesn't
have cvsnt support...
>
>> - the protocol is never being changed. When it was :pserver:
>> before, it's gonna stick with :pserver:, even if I switch to a
>> :ext: CVSROOT using the previous CVSROOT menu
>
> This is because CVS is actually ignoring what we tell it and it's
> using the
> cached value from CVS/Root file. One more example why there is no
> point to
> have CVSROOT in the preferences.
I agree that at the very least, the current setup is confusing.
However, I found that for some commands, cvs seems to not ignore the
CVSROOT and it's actually not correct, but I'll have to do a bit more
tests when exactly that happens... those commands will definitely need
the CVSROOT as an input.
>
> The timeframe for that changes in "now". I already have a working
> version
> without any CVSROOT preferences in my sandbox. It will take me a few
> more
> days to change the command dialogs affected and also to make the
> transition
> easier for MacCvs and gCvs. I will wrap the changes into a #ifdef so
> you
> will have time to adjust the code and switch to the new CVSROOT
> handling. I
> will announce the details once I'm done.
Thanks for the info.
</jum>
[Non-text portions of this message have been removed]
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/NhFolB/TM
---------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/cvsgui-dev/
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/