Author Topic: CVS pserver support - modules vs. top-level directories?  (Read 5565 times)

schumann

  • Community Member
  • Posts: 5
  • Hero Points: 0
CVS pserver support - modules vs. top-level directories?
« on: November 09, 2009, 07:34:35 PM »
Hi,

I am trying to check out source code from CVS using slickedit's built in CVS support.  In our case pserver is being used for authentication.   The CVS Setup and login seem to go OK, but the checkout has some surprising results at least to me.
The "Check Out Module ..." dialog however does not list modules from CVSROOT/modules but instead the top-level directories within CVS.   It does not allow me to enter an explicit module name.   So I am a little confused by the use of the term module within slickedit it does not appear to used in the same way the CVS uses the term.    Any explanation please?

Thanks,
Carl Schumann

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2929
  • Hero Points: 153
Re: CVS pserver support - modules vs. top-level directories?
« Reply #1 on: November 12, 2009, 01:30:33 AM »
Are there aliases setup in your CVS modules?  If so, we may not be able to get these.

CVS provides no mechanism to list modules.  We wanted to provide this, and eventually stumbled on to a way to do that generally works.  It is not perfect, and of course it is something that CVS never really supported.  So it may be easier to check this module out from the command line.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2929
  • Hero Points: 153
Re: CVS pserver support - modules vs. top-level directories?
« Reply #2 on: November 12, 2009, 04:28:20 PM »
Quote
hen use "Check Out Modules" under Tools -> Version Control, I see the following printed to the terminal window:
nova:~ $ vs
U .vscvsinfo/modules
nova:~ $

When I go poking around under ~/.slickedit I find our modules file checked out as:
nova:~ $ ls ~/.slickedit/13.0.2/.vscvsinfo/modules
/export/home/schumann/.slickedit/13.0.2/.vscvsinfo/modules
nova:~ $

I cat'ed the file above and it is indeed our non-empty modules files:
nova:~ $ tail ~/.slickedit/13.0.2/.vscvsinfo/modules
clx             misc/sysman/linux/clx
sdaii           gov/fnal/sda
central         misc/sysman/linux/central
dce             misc/sysman/linux/dce
firus-console   misc/firus/console
firus-server    misc/firus/server
fileserver      misc/sysman/linux/fileserver
java_apps_srv   misc/sysman/linux/java_apps_srv
esh             misc/sysman/linux/esh
backup_srv      misc/sysman/linux/backup_srv
nova:~ $

I am thinking about buying current versions of slickedit for a different machine, but hesitate to do without a resolution to CVS interoperability.

Thanks,
Carl Schumann

Are the directories listed in the dialog the ones mapped from this file?

schumann

  • Community Member
  • Posts: 5
  • Hero Points: 0
Re: CVS pserver support - modules vs. top-level directories?
« Reply #3 on: November 12, 2009, 08:25:44 PM »
No.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2929
  • Hero Points: 153
Re: CVS pserver support - modules vs. top-level directories?
« Reply #4 on: November 13, 2009, 01:51:51 PM »
What is listed, and what did you expect?

schumann

  • Community Member
  • Posts: 5
  • Hero Points: 0
Re: CVS pserver support - modules vs. top-level directories?
« Reply #5 on: November 16, 2009, 01:00:32 PM »
What I see:
.settings
AppsRunFiles
CVSROOT
bin
buildtools
cert
com
commons
docs
engines
gov
jCVS
jars
misc
org
src
test
thinlet
tomcatroot
uk
webstart
www-bd

What I expect:
sysman
ntf
midamper
govtree
applications
oacs
examples
irm
penumbra
clx
sdaii
central
dce
firus-console
firus-server
fileserver
java_apps_srv
esh
backup_srv