$CVSROOT/CVSROOT scripts

2004-06-21 Thread Christopher.Fouts
Ok what's the proper way of putting scripts into this
directory that the cvs files can use. For example I want
to call a buglog.sh file from the loginfo file. Do I
- checkout the $CVSROOT/CVSROOT directory
- cvs add buglog.sh file
- modify loginfo to call the buglog.sh file
- cvs commit
- cp ../CVSROOT/buglog.sh,v ../CVSROOT/buglog.sh (???)
- Remove RCS info from buglog.sh (???)
- Ensure correct rwx permissions for ../CVSROOT/buglog.sh

The two step with the (???) is what I'm iffy about. Also
how come subsequent changes made to buglog.sh (ie, after
cvs co, modify, cvs commit) not show up in the repository?

--
Chris T Fouts


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


Re: $CVSROOT/CVSROOT scripts

2004-06-21 Thread Geoff Beier
On Jun 21, 2004, at 1:54 PM, [EMAIL PROTECTED] wrote:
Ok what's the proper way of putting scripts into this
directory that the cvs files can use. For example I want
to call a buglog.sh file from the loginfo file. Do I
- checkout the $CVSROOT/CVSROOT directory
- cvs add buglog.sh file
- modify loginfo to call the buglog.sh file
- cvs commit
So far, so good. Now you need to add it to the checkoutlist file:
https://www.cvshome.org/docs/manual/cvs-1.11.6/cvs_18.html#SEC176
HTH,
Geoff

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


Re: $CVSROOT/CVSROOT scripts

2004-06-21 Thread Larry Jones
[EMAIL PROTECTED] writes:
 
 Ok what's the proper way of putting scripts into this
 directory that the cvs files can use.

As usual, the answer begins with That depends  If you don't care
about revision control on the scripts, then you can just copy them into
the directory.  If you do want revision control, then you need to follow
the basic process you outlined with just a few corrections:

 - checkout the $CVSROOT/CVSROOT directory
 - cvs add buglog.sh file

Set the permissions the way you want them now and CVS will preserve them
for you.

 - modify loginfo to call the buglog.sh file

Also modify the checkoutlist file to include your new file.

 - cvs commit

OK.

 - cp ../CVSROOT/buglog.sh,v ../CVSROOT/buglog.sh (???)
 - Remove RCS info from buglog.sh (???)

No.  If you added your file to checkoutlist, CVS should check it out
automatically.  (And will do so every time to commit changes to it in
the future.)  If you neglected to do that, simply do so now and CVS will
checkout your file when you checkin the change to checkoutlist.

 - Ensure correct rwx permissions for ../CVSROOT/buglog.sh

A good idea, but it shouldn't be necessary if you set them correctly
before checking it in the first time.  If you neglected to do that, you
can set the permissions on the RCS file and CVS should copy them to the
checkout out file in the future.

-Larry Jones

If I was being raised in a better environment, I wouldn't
do things like that. -- Calvin


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


Re: $CVSROOT/CVSROOT scripts

2004-06-21 Thread Frederic Brehm
At 02:07 PM 6/21/2004, Larry Jones wrote:
If you don't care
about revision control on the scripts

Horrors! Heretic!
:-)
Fred
___
Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/

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


RE: $CVSROOT/CVSROOT scripts

2004-06-21 Thread Christopher.Fouts

 - Ensure correct rwx permissions for ../CVSROOT/buglog.sh

A good idea, but it shouldn't be necessary if you set them 
correctly before checking it in the first time.  If you 
neglected to do that, you can set the permissions on the RCS 
file and CVS should copy them to the checkout out file in the future.


Sorry I missed this. Where in the RCS files? I see access; so I'm
assuming it's there, but set to what? 

-chris


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


Re: $CVSROOT/CVSROOT scripts

2004-06-21 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[EMAIL PROTECTED] writes:

 
  - Ensure correct rwx permissions for ../CVSROOT/buglog.sh
 
 A good idea, but it shouldn't be necessary if you set them 
 correctly before checking it in the first time.  If you 
 neglected to do that, you can set the permissions on the RCS 
 file and CVS should copy them to the checkout out file in the future.
 
 
 Sorry I missed this. Where in the RCS files? I see access; so I'm
 assuming it's there, but set to what? 

chmod a+x $CVSROOT/CVSROOT/buglog.sh,v

-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFA108/3x41pRYZE/gRAigLAJ9SWn75Bu6vgCfyH5F+2FVBqrYTCwCgqBPJ
VDSGY6qGebRgj5RpCZImt94=
=UmH4
-END PGP SIGNATURE-


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


Re: $CVSROOT/CVSROOT scripts

2004-06-21 Thread Larry Jones
[EMAIL PROTECTED] writes [quoting me]:
 
 If you 
 neglected to do that, you can set the permissions on the RCS 
 file and CVS should copy them to the checkout out file in the future.
 
 Sorry I missed this. Where in the RCS files? I see access; so I'm
 assuming it's there, but set to what? 

Not *in* the RCS file, *on* the RCS file.  CVS uses the RCS file's
permissions as the template for the checked-out file's permissions.

-Larry Jones

I always send Grandma a thank-you note right away.  ...Ever since she
sent me that empty box with the sarcastic note saying she was just
checking to see if the Postal Service was still working. -- Calvin


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


RE: $CVSROOT/CVSROOT scripts

2004-06-21 Thread Christopher.Fouts
Yes thanks you. A couple of folks have pointed that out
already and I did a Duhhh response. So I did this and
it worked, but it worked too good. I set the perms.
on the RCS file to r-xr-x---, but when I checked out/
checked in/commit, RCS file had r-xr-xr-- (gave read
permission to others). Why? Again CVSUMASK is set to
007.

-chris

-Original Message-
From: Larry Jones [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 21, 2004 5:17 PM
To: Fouts Christopher ()
Cc: [EMAIL PROTECTED]
Subject: Re: $CVSROOT/CVSROOT scripts


[EMAIL PROTECTED] writes [quoting me]:
 
 If you
 neglected to do that, you can set the permissions on the RCS 
 file and CVS should copy them to the checkout out file in 
the future.
 
 Sorry I missed this. Where in the RCS files? I see access; so I'm 
 assuming it's there, but set to what?

Not *in* the RCS file, *on* the RCS file.  CVS uses the RCS 
file's permissions as the template for the checked-out file's 
permissions.

-Larry Jones

I always send Grandma a thank-you note right away.  ...Ever 
since she sent me that empty box with the sarcastic note 
saying she was just checking to see if the Postal Service was 
still working. -- Calvin



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