Re: Re: Re: wrapper funcs to cvs cmds

2002-11-19 Thread mehul choube
Not quite sure why you would need this, but maybe
expect will do your thing.

	i m working on a product which need a good data
storage. now we decided to go for cvs as a data storage.
now the product GUI is written in VB. now i want this
VB prog to call cvs commands. for this i thougt the best
way will be to write a DLL of wrapper funcs on existing
cvs cmds in C programming language. i think the same is
done in wincvs. expect is one way to do but how this can
be done without using expect? i would like to do it
without using expect. how this can be done using IPC?
any one with experience in developing cvs client will
be of much help.

mehul.
__
Give your Company an email address like
ravi @ ravi-exports.com.  Sign up for Rediffmail Pro today!
Know more. http://www.rediffmailpro.com/signup/



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Branches and Dates

2002-11-19 Thread Mark . Hewitt


I thought I understood this, but the evidence is against me ...

We have a situation where we need to see the state of a branch
at a point of time in the past.  Problem is that if I checkout
the branch and then update ... -D date ... what I appear to get
is the state of the module at that date with the branches collapsed.
For example, a file that existed only on the trunk mysteriously
appears in the branch if I use a date after the time it was added
to the trunk.

So what are the interactions between branches and dates?

#!/mjh




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



problem while checking out a file

2002-11-19 Thread Jaya Kumari
Hi all,
I have a system user and cvs user with the same name.
And i have a group CVS with users who can access the repoistory.
I have changed the group of the repoistory folder to CVS.
When i try to checkout a file it is giving me the following error.

cvs checkout -P uClinux-dist/config.in (in directory C:\)
cvs checkout: Empty password used - try 'cvs login' with a real password

cvs [checkout aborted]: authorization failed: server 172.16.12.152 rejected
access to /opt for user ssatya

ssatya is a user in the group CVS.

the folder permissions are as follows :
drwxrwxr-x3 rtslinux CVS  4096 Nov 14 19:56 CVSROOT
drwxrwxr-x   17 rtslinux CVS  4096 Nov 14 20:10 uClinux-dist

the /etc/group file has the following entries :
rtslinux:x:501
ssatya:x:503
CVS:x:505:ssatya,rtslinux

not able to figure what is the problem.




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Newbie question re: ssh

2002-11-19 Thread Robert Koster
So, one of the pros of this approach is that it is more secure than the :pserver 
method, because the passwords are being transmitted over ssh?  One of the cons is 
that the password will need to be entered frequently?


 Greg A. Woods [EMAIL PROTECTED] 11/16 2:20 PM 
[ On Friday, November 15, 2002 at 22:20:39 (-0800), Mike Ayers wrote: ]
 Subject: Re: Newbie question re: ssh

 Robert Koster wrote:
 
  I have set up a repository, and want to use :ext w/ SSH (without
   keys).  Pros/cons?
 
   Con:  this isn't possible.  ssh operating without keys will forcibly 
 invoke username/password login, which will gag the CVS client.

Huh?  I haven't tried without keys in a while but I'm pretty sure my
client still just asks me for the password and lets me type it

-- 
Greg A. Woods

+1 416 218-0098;[EMAIL PROTECTED];   [EMAIL PROTECTED]
Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]


___
Info-cvs mailing list
[EMAIL PROTECTED] 
http://mail.gnu.org/mailman/listinfo/info-cvs



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Newbie question re: ssh

2002-11-19 Thread Kenneth Loafman
No.  You can set up the CVS server and the client side with passwordless 
access via RSH keys.  It's in the SSH docs.  That way you never have to 
enter a password after SSH is set up.

...Ken

Robert Koster wrote:
So, one of the pros of this approach is that it is more secure than the :pserver method, because the passwords are being transmitted over ssh?  One of the cons is that the password will need to be entered frequently?




Greg A. Woods [EMAIL PROTECTED] 11/16 2:20 PM 



[ On Friday, November 15, 2002 at 22:20:39 (-0800), Mike Ayers wrote: ]


Subject: Re: Newbie question re: ssh

Robert Koster wrote:



I have set up a repository, and want to use :ext w/ SSH (without


 keys).  Pros/cons?

	Con:  this isn't possible.  ssh operating without keys will forcibly 
invoke username/password login, which will gag the CVS client.


Huh?  I haven't tried without keys in a while but I'm pretty sure my
client still just asks me for the password and lets me type it







___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Branches and Dates

2002-11-19 Thread Larry Jones
[EMAIL PROTECTED] writes:
 
 We have a situation where we need to see the state of a branch
 at a point of time in the past.  Problem is that if I checkout
 the branch and then update ... -D date ... what I appear to get
 is the state of the module at that date with the branches collapsed.
 For example, a file that existed only on the trunk mysteriously
 appears in the branch if I use a date after the time it was added
 to the trunk.

You need to specify both the branch and the date.  Unfortunately, not
all CVS subcommands allow both -D and -r at the same time, but I believe
that update is one that does, despite what the documentation may say.

-Larry Jones

Aw Mom, you act like I'm not even wearing a bungee cord! -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: How to make update -d ignore a top-level directory?

2002-11-19 Thread Larry Jones
Shankar Unni writes:
 
 * Be able to sit at the root of my work area (where I did the cvs
 checkout), and be able to do a simple cvs update -d.
 * Have the cvs update -d fetch everything except a single top-level
 directory I don't want.

Unfortunately, that is not possible with the current design of CVS. 
There is no way for update to distinguish between a newly-added
directory and an old directory that you explicitly chose not to check
out in the first place.

-Larry Jones

You just can't ever be too careful. -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: problem while checking out a file

2002-11-19 Thread Larry Jones
Jaya Kumari writes:
 
 cvs checkout -P uClinux-dist/config.in (in directory C:\)
 cvs checkout: Empty password used - try 'cvs login' with a real password
 
 cvs [checkout aborted]: authorization failed: server 172.16.12.152 rejected
 access to /opt for user ssatya

That means that either the username and password or the repository you
specified were not valid.  Since you got a message saying that you
didn't specify a password at all, my guess would be that that's the
problem.

-Larry Jones

My life needs a rewind/erase button. -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Newbie question re: ssh

2002-11-19 Thread Jenn Vesperman
On Wed, 2002-11-20 at 00:25, Robert Koster wrote:

   I have set up a repository, and want to use :ext w/ SSH (without
keys).  Pros/cons?
  
  Con:  this isn't possible.  ssh operating without keys will forcibly 
  invoke username/password login, which will gag the CVS client.
 
 Huh?  I haven't tried without keys in a while but I'm pretty sure my
 client still just asks me for the password and lets me type it

Apparently some of the graphic clients don't understand the password
prompt. The command line client is fine, though.



Jenn V.
-- 
Do you ever wonder if there's a whole section of geek culture 
you miss out on by being a geek? - Dancer.

[EMAIL PROTECTED] http://anthill.echidna.id.au/~jenn/




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Deleting a module

2002-11-19 Thread Giohanna MEndez
Hi,

How can I delete a module in the repository?

Regards,
  Giohanna

_
Charla con tus amigos en lĂ­nea mediante MSN Messenger: 
http://messenger.microsoft.com/es



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Deleting a module

2002-11-19 Thread Mahantesh
Giohanna MEndez wrote:
 How can I delete a module in the repository?
Just backup that module and remove it from the repository.

-Mahantesh.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



RE: How to make update -d ignore a top-level directory?

2002-11-19 Thread Shankar Unni
Larry Jones writes:

 Unfortunately, that is not possible with the current design of CVS. 

That's what I figured. Oh well, time for a module move. 

Actually, what I really need to do is to reorganize the top-level
modules - the mistake was that our original core code was not neatly
checked in in the form of a module; instead, all the top-level
directories under our source tree (src, lib, doc) were checked in as
modules.

Sigh! Thanks all,
--
Shankar.



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Newbie question re: ssh

2002-11-19 Thread Greg A. Woods
[ On Tuesday, November 19, 2002 at 08:25:45 (-0500), Robert Koster wrote: ]
 Subject: Re: Newbie question re: ssh

 So, one of the pros of this approach is that it is more secure than
 the :pserver method, because the passwords are being transmitted over
 ssh?

The password encapsulation and obfuscation is really only a small part
of the whole transport layer security issue.  TCP is not secure (in any
meaning of that word), at least not alone over plain old IPv4.

Even the transport security is only a small part of the whole CVS
security issue.  CVS is not designed or implemented to be a security
tool -- it's at the level of /bin/ed in security terms, not /bin/login.
With CVSpserver there's lots of opportunity for one user to spoof
another -- i.e. there's _NO_ accountability in pserver.

  One of the cons is that the password will need to be entered
 frequently?

SSH can be configured to use any of many forms of authentication.
There's no fundamental need to ever type passwords to it when it's used
as a remote job execution facility for CVS.

-- 
Greg A. Woods

+1 416 218-0098;[EMAIL PROTECTED];   [EMAIL PROTECTED]
Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: New member

2002-11-19 Thread Larry Jones
Patrick Malaison writes:
 
 I am a new member of the list as well as of CVS. I am reading through 
 the Open source development book and also ordered the Quick reference 
 guide. Do you have any other suggestions for primer?

I suggest reading through the manual, if you haven't already:

http://www.cvshome.org/docs/manual/cvs.html

 My goal is to set it up as a remote CVS server. How's the security using 
 pserver, what is the best client giving the fact that I will have a 
 multi-OS user bed?

There is no security using pserver.  Use the :ext: method with SSH
(secure shell) rather than RSH as the transport.

-Larry Jones

My dreams are getting way too literal. -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



RE: New member

2002-11-19 Thread Zieg, Mark
 Patrick Malaison writes:
 
 My goal is to set it up as a remote CVS server. How's the security using 
 pserver, what is the best client giving the fact that I will have a 
 multi-OS user bed?

As has been said, ssh rocks.

The other part of your question doesn't make a lot of sense, if you think
about it.

 What's the best language to use, given that
  I will have an international user bed?

Obviously, the best client will depend on what OS the user is using.
*You* can use whatever client you want.

Also, best client depends on the what the user likes.  Power-users will
probably find the command-line cvs clients available for Linux, FreeBSD,
Cygwin, OS-X, etc perfectly servicable.  Others may feel drawn to the GUI
clients made for most platforms.  Web clients exist that run on every
platform that runs a browser.  Best isn't much criteria to go by...they
*all* work.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: New member

2002-11-19 Thread Patrick Malaison




Thanks for the info although you quoted me wrong on my second question, your
answer made sense. So to be more specific, I will be setting up CVS for a
multi platform, multi OS environment where the developers will work either/or
remotely in the office, some of them are very junior and some of them highly
experience. I will also be supporting those users so I was thinking of using
a web client so that I would only have to support one CVS client.

By best I meant easy to support, easy to learn, lots of functionality and
a high quality product that is stable, and offer good security . Do any of
the web clients fit that bill?

Zing, Mark wrote:

  
Patrick Malaison writes:

My goal is to set it up as a remote CVS server. How's the security using 
pserver, what is the best client giving the fact that I will have a 
multi-OS user bed?

  
  
As has been said, ssh rocks.

The other part of your question doesn't make a lot of sense, if you think
about it.

 "What's the best language to use, given that
  I will have an international user bed?"

Obviously, the "best" client will depend on what OS the user is using.
*You* can use whatever client you want.

Also, "best" client depends on the what the user likes.  Power-users will
probably find the command-line cvs clients available for Linux, FreeBSD,
Cygwin, OS-X, etc perfectly servicable.  Others may feel drawn to the GUI
clients made for most platforms.  Web clients exist that run on every
platform that runs a browser.  "Best" isn't much criteria to go by...they
*all* work.

  


-- 
Patrick Malaison
mailto:[EMAIL PROTECTED]







___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


RE: New member

2002-11-19 Thread Zieg, Mark
 Thanks for the info although you quoted me wrong on my second question,
your answer made sense. 

'twas meant as an analogy.  s'okay, you mispelled my name :-)

 So to be more specific, I will be setting up CVS for a multi platform,
 multi OS environment where the developers will work either/or remotely
 in the office, some of them are very junior and some of them highly
 experience. I will also be supporting those users so I was thinking
 of using a web client so that I would only have to support one CVS client.
 
There are fans of both WinCVS and jCVS.  I'm not a GUI user myself, but in
those cases where I had to choose, I prefer the Java GUI clients because
then (as you indicated) I only had one client to support for any platform
(Windows, Linux, Mac, etc).

If your junior coders know how to use vi, then they could certainly handle
cmd-line cvs.  On the other hand, if they live and breathe in TextPad or
some other Windows editor, then WinCVS or jCVS would seem to fit the bill.

You may consider this an opportunity to upgrade the skills of your junior
coders.  I've been in a situation similar to yours a couple of times, and
what we did in each case was take a week to teach the junior members how to
use Cygwin (or U/Win, in one shop), or true telnet/ssh to a Unix dev box,
and make the investment in training the team to learn how to use a real
development environment.

Most were able to make the transition, and the whole group benefited as a
result.  Those who couldn't learn how to work in a command-line
environment...well, perhaps t'were best that those mis-hires were identified
sooner rather than later.  It's a tough world.

Any client -- any at all -- should be able to bridge the working locally vs
working remotely gap.

 By best I meant easy to support, easy to learn, lots of functionality
 and a high quality product that is stable, and offer good security. Do
 any of the web clients fit that bill?

I'm not aware of any web-based client that is good for anything except
browsing the tree (as opposed to real development).  Besides, the security
of any web-based client would be entirely dependent on whether you had an
SSL certificate for HTTP/S, or a private VPN/intranet, etc.

-MZ


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Branches and Dates

2002-11-19 Thread Eric Siegerman
On Tue, Nov 19, 2002 at 10:16:47AM -0500, Larry Jones wrote:
 You need to specify both the branch and the date.  Unfortunately, not
 all CVS subcommands allow both -D and -r at the same time [...]

Why not?  I could see the reason being any of:
 a. because they don't always make sense together
 b. a thing that could be fixed simply if someone were motivated
 c. a thing that could be fixed, but only with difficulty
 d. a thing that should be fixed, but cannot be, due to
insurmountable internal problems
or even different situations for the different subcommands.

Please don't take this as criticism, Larry; that's not my intent!
I'm merely trying to draw you out on the reasons.  It'd be good
to have that bit of your expertise on the record, in case someone
tripping across this thread in the archives decides it's a
project worth taking on :-)

--

|  | /\
|-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
Just Say No to the faceless cannonfodder stereotype.
- http://www.ainurin.net/ (an Orc site)


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Branches and Dates

2002-11-19 Thread Larry Jones
Eric Siegerman writes:
 
 On Tue, Nov 19, 2002 at 10:16:47AM -0500, Larry Jones wrote:
  You need to specify both the branch and the date.  Unfortunately, not
  all CVS subcommands allow both -D and -r at the same time [...]
 
 Why not?

Existing inconsistency coupled with profound indecision over exactly how
to best provide the capability.  Some places in CVS allow you to specify
a branch and a date in a single package, like update -j's branch:date
syntax.  Other places, like update, allow specifying -r and -D at the
same time.  Still other places, most notably diff, allow -r and -D at
the same time, but interpret them as specifying two different revisions
rather than jointly specifying a single revision.  Trying to unify all
that is a daunting task, particulary when you try to ensure that the
result will be upward compatible (for all of clients, servers, and
users).

-Larry Jones

That's one of the remarkable things about life.  It's never so
bad that it can't get worse. -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: Branches and Dates

2002-11-19 Thread Jenn Vesperman
On Wed, 2002-11-20 at 10:06, Larry Jones wrote:
 Eric Siegerman writes:
  
  On Tue, Nov 19, 2002 at 10:16:47AM -0500, Larry Jones wrote:
   You need to specify both the branch and the date.  Unfortunately, not
   all CVS subcommands allow both -D and -r at the same time [...]
  
  Why not?
 
 Existing inconsistency coupled with profound indecision over exactly how
 to best provide the capability.  Some places in CVS allow you to specify
 a branch and a date in a single package, like update -j's branch:date
 syntax.  Other places, like update, allow specifying -r and -D at the
 same time.  Still other places, most notably diff, allow -r and -D at
 the same time, but interpret them as specifying two different revisions
 rather than jointly specifying a single revision.  Trying to unify all
 that is a daunting task, particulary when you try to ensure that the
 result will be upward compatible (for all of clients, servers, and
 users).

Thank you for clarifying that.

Hrm. Given that some places (such as diff) need to be able to specify -r
and -D to mean two distinct revisions, would the branch:date syntax be
the most effective answer?

And given that it's an expansion of functionality, is there a problem
with implementing it in the next version and then allowing other
development teams to add it as they go?



Jenn V.
-- 
Do you ever wonder if there's a whole section of geek culture 
you miss out on by being a geek? - Dancer.

[EMAIL PROTECTED] http://anthill.echidna.id.au/~jenn/




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: New member

2002-11-19 Thread P. Fleury
Zieg, Mark wrote:


Thanks for the info although you quoted me wrong on my second question,
   

your answer made sense. 

'twas meant as an analogy.  s'okay, you mispelled my name :-)

 

So to be more specific, I will be setting up CVS for a multi platform,
multi OS environment where the developers will work either/or remotely
in the office, some of them are very junior and some of them highly
experience. I will also be supporting those users so I was thinking
of using a web client so that I would only have to support one CVS client.
   


There are fans of both WinCVS and jCVS.  I'm not a GUI user myself, but in
 

To add my salt to this soup, I'd say also that some IDE have this 
functionality well integrated. For example NetBeans, the Java IDE, has 
it well integrated and is really easy to use. But if you don't develop 
Java, you may or may not have it in the IDE you users select. WinCVS and 
jCVS are fine tools, but they are eparate from the IDE, which users may 
or may not like.

--Pascal

 





___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs