Re: Updated cvs_acls2 Access Control List script

[Derek Robert Price]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Peter Connolly wrote:

>Thanks to the feedback on the first release of this script.  
>
>In particular, I'd like to thank Karl-Konig Konigsson for sending me
debug trace with his emails.
>
>Thanks to Derek Robert Price and Mark D. Baushke for the help on how to
submit this script to 'contrib'.  (Do these guys ever sleep?)
>
>I've posted the updated script as issue #170 on the ccvs Issuezilla.
Since the last drop on Feb. 26 we've fixed some errors in "global"
restrictions; refactored some duplicate code; fixed the date/time stamp
in the restricted_log file output; reformatted the code comments into
pod format; and many others.
>
>I also posted the script comments in pod2html format. It lists the
updated installation, configuration, program logic and licensing
information.
>
>As usual, any input, feedback, corrections or suggestions you have are
welcome.
>
>Thanks,
>pc


I don't actually use this script.  Would someone who does mind reviewing
Peter's changes?  Should I really check this in as a separate script or
can I just update the old version and assume anyone who needs something
older either already has it or can find the version in the repository?
Ville?  Aaron?  Anybody?

Derek

- --
*8^)

Email: [EMAIL PROTECTED]

Get CVS support at !
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFAa2TKLD1OTBfyMaQRAo27AJ4/a8a59rw0Id3qNKBq6C9NdqxX6ACePuIi
7wCXtaJexL9nzy1fHLTBvoc=
=elPD
-END PGP SIGNATURE-




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

Re: renaming a Repository

[Johnny Fulcrum]

On Wed, 31 Mar 2004 14:41:59 -0800, Conrad T. Pino <[EMAIL PROTECTED]> wrote:

From: Johnny Fulcrum

Is renaming a repository as easy as mv   at the UNIX
command line and letting anyone who has
things checked out know they have to fix up all of the CVS/Root files in
their sandboxes as well as their ~/.cvspass files if for pserver?
That's almost true.  Since/if you're using :pserver: on the server side  
then
you need to modify "inetd.conf" option "--allow-root=" value.  Read this:
http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_2.html#SEC30

Yes That is true!  Forgot to mention I have a inetd.conf hack to run a  
shell to dynamically grab any directory in a certain location and treat it  
as a repository:
/usr/bin/cvs -f  `ls -d /cvs/* | sed -e '1,$s/.*/--allow-root=&/'` pserver

Then I don't have to have the unix admins edit the inetd.conf file... :)

Also consider cvs will use repositories identified by symbolic links and
accepts multiple "--allow-root=" options.  Consider doing:
   mv# new name is hard linked
   ln# old name is symbolic link
In "inetd.conf" use "--allow-root= --allow-root=" and
then access by old AND new names should work concurrently.
concerned about history - but I see nothing in CVSROOT that is depending
on the name of the repository...
Don't know about this one myself.





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

RE: renaming a Repository

[Conrad T. Pino]

> From: Johnny Fulcrum
> 
> Is renaming a repository as easy as mv   at the UNIX  
> command line and letting anyone who has
> things checked out know they have to fix up all of the CVS/Root files in  
> their sandboxes as well as their ~/.cvspass files if for pserver?

That's almost true.  Since/if you're using :pserver: on the server side then
you need to modify "inetd.conf" option "--allow-root=" value.  Read this:
http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_2.html#SEC30

Also consider cvs will use repositories identified by symbolic links and
accepts multiple "--allow-root=" options.  Consider doing:

   mv# new name is hard linked
   ln# old name is symbolic link

In "inetd.conf" use "--allow-root= --allow-root=" and
then access by old AND new names should work concurrently.

> concerned about history - but I see nothing in CVSROOT that is depending  
> on the name of the repository...

Don't know about this one myself.



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

renaming a Repository

[Johnny Fulcrum]

Is renaming a repository as easy as mv   at the UNIX  
command line and letting anyone who has
things checked out know they have to fix up all of the CVS/Root files in  
their sandboxes as well as their ~/.cvspass files if for pserver?

concerned about history - but I see nothing in CVSROOT that is depending  
on the name of the repository...

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

RE: Versioning between checkout|update, commit

[Paul Sander]

Some shops also implement a handoff mechanism that divorces the notion
of "latest committed" from "candidate for integration".  That allows
the developers to commit with impunity without fear that the world
would see something inappropriately.

--- Forwarded mail from [EMAIL PROTECTED]

Create your own private branch to do work on.  When you want to save
work, commit the code.
When you are done, merge the changes down.  

Other possibilities include implementing a backup system that takes
hourly snapshots

--- End of forwarded message from [EMAIL PROTECTED]



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

Re: cvs.spec(.in) is causing an error building rpms

[Mark D. Baushke]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Geoff Beier <[EMAIL PROTECTED]> writes:

> > Does this patch work for you?
> >
> That does the job as well. Thanks.

Thanks for checking.

I have committed the fix to the stable and feature branches.

Enjoy!
-- Mark

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

iD8DBQFAaxpp3x41pRYZE/gRAoKNAJwJo+zDzUkMEDZnQ4Y50NXyCB9voQCeOBmy
K0Mv6LjOoOejyh8qLEc1864=
=zJQ1
-END PGP SIGNATURE-


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

Re: cvs.spec(.in) is causing an error building rpms

[Geoff Beier]

Hi Mark,

Does this patch work for you?

That does the job as well. Thanks.

Geoff


smime.p7s
Description: S/MIME Cryptographic Signature
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Versioning between checkout|update, commit

[Donald Sharp \(sharpd\)]

Create your own private branch to do work on.  When you want to save
work, commit the code.
When you are done, merge the changes down.  

Other possibilities include implementing a backup system that takes
hourly snapshots

Find what works best for you, of course.

donald
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hugh
Sasse Staff Elec Eng
Sent: Wednesday, March 31, 2004 12:39 PM
To: [EMAIL PROTECTED]
Subject: Versioning between checkout|update, commit


Still a newbie, I'd like to know how people tackle changing code they
are not ready to commit.  How does one maintain versions of changes one
has made to one's working copy of code, before one has reached the stage
of doing a commit?

It would be possible to use SCCS for this, I suppose, as I think it's
keyword tags are based on @() rather than $$, but this means keeping two
sets of commands in one's head at once, when they perform much the same
function.  I think this would be error prone. RCS uses the same
information in files as CVS and would therefor conflict.

I've searched the faqs and the last 3 months of the list for likely
subjects, but my keyword searches were less than adequate

Thank you,
Hugh



___
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: Versioning between checkout|update, commit

[Fouts Christopher (6452)]

With a branch, ie, commit code you're not ready to "integrate" on you
own branch!

-chris

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Hugh Sasse Staff Elec Eng
Sent: Wednesday, March 31, 2004 12:39 PM
To: [EMAIL PROTECTED]
Subject: Versioning between checkout|update, commit


Still a newbie, I'd like to know how people tackle changing code they are
not ready to commit.  How does one maintain versions of changes one has made
to one's working copy of code, before one has reached the stage of doing a
commit?

It would be possible to use SCCS for this, I suppose, as I think it's
keyword tags are based on @() rather than $$, but this means keeping two
sets of commands in one's head at once, when they perform much the same
function.  I think this would be error prone. RCS uses the same information
in files as CVS and would therefor conflict.

I've searched the faqs and the last 3 months of the list for likely
subjects, but my keyword searches were less than adequate

Thank you,
Hugh



___
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

Versioning between checkout|update, commit

[Hugh Sasse Staff Elec Eng]

Still a newbie, I'd like to know how people tackle changing code
they are not ready to commit.  How does one maintain versions of
changes one has made to one's working copy of code, before one has
reached the stage of doing a commit?

It would be possible to use SCCS for this, I suppose, as I think
it's keyword tags are based on @() rather than $$, but this means
keeping two sets of commands in one's head at once, when they
perform much the same function.  I think this would be error prone.
RCS uses the same information in files as CVS and would therefor
conflict.

I've searched the faqs and the last 3 months of the list for likely
subjects, but my keyword searches were less than adequate

Thank you,
Hugh



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

Re: locking a file exclusively

[Derek Robert Price]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Paul Gelderblom (ptok) wrote:

>The latest version of that patch (kept in synch with the CVS sources by
>Matthew Ogilvie)
>can be found on
>http://sourceforge.net/tracker/index.php?func=detail&aid=822306&group_id=20011&atid=320011
>Or: The "patches" link under
>http://sourceforge.net/projects/cvsenhancements/
>There are multiple versions of the patch on that page; please make
>sure you download the latest one (21feb2004).
>
>Actually, Derek Price is currently working on incorporating it in the
>mainstream CVS.


I was.  I'm going to be extremely busy through July, so if anyone else
wants to pick this up they are welcome to.  I imported all the small bug
fixes that were part of this patch (um, maybe I skipped one, but I think
I had a good reason and sent an email about it to someone... Paul?
Mark?  The list?) but was again daunted by the size of the major portion
of this patch.  It will probably only take me a day or two to figure out
when I get back around to it, so I'll pick it up again when I have time.

Unless someone can figure out some way it makes sense to break it up
into even smaller chunks, so that I can spend an hour here and an hour
there reviewing and approving the change, it might be July before I can
get back to it.

Derek

- --
*8^)

Email: [EMAIL PROTECTED]

Get CVS support at !
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFAaudhLD1OTBfyMaQRAo58AKDUb1Z5g9ee4EthhENJ30uH9H6z/QCg1f97
Zt9nqdU9jnH0cyVEXqlwXGY=
=5vYN
-END PGP SIGNATURE-




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

RE: removal of branch

[Fouts Christopher (6452)]

Title: Message



Quote 
from Essential CVS by Jennifer Vesperman:
"Unless the branch has just been created and no work has been done on it, 
I recommend against deleting or moving a branch. Most tags can be deleted or 
moved without affecting a project's history, but changes on a branch become part 
of the change record of each file in the branch." (p. 86 of 2003 1st 
edition)
 
> 
cvs tag -d -B 
 
-chris

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf 
  Of Ramanuj SinghSent: Wednesday, March 31, 2004 5:18 
  AMTo: '[EMAIL PROTECTED]'Subject: removal of 
  branch
  How can we remove branch from a project 
  The information transmitted is intended only for the person or 
  entity to whom it is addressed and may contain confidential and / or 
  privileged Material. Any review, re-transmission, dissemination or other use 
  of or taking of any action in reliance upon, this information by persons or 
  entities other than the intended recipient is prohibited. If you received this 
  in error, please contact the sender and delete the material from your 
  computer. Thank you for your understanding & co-operation. 

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

Re: removal of branch

[Larry Jones]

Ramanuj Singh writes:
> 
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.

Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!

> How can we remove branch from a project

Why do you want to do that?  The whole point of a revision control
system is to preserve history, so you usually don't want to really
remove anything.

-Larry Jones

I take it there's no qualifying exam to be a Dad. -- Calvin


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

Re: locking a file exclusively

[Paul Gelderblom \(ptok\)]

> Failing that, there are various patches that try to implement strict
> locking on top of cvs floating around out there, a search for "cvs edit
> - -c" might turn up Noel Yap's patches... I have not looked at them in a
> long time... once upon a time there was an rcvs sourceforge.net project,
> but I can't seem to find it this evening.
>
The latest version of that patch (kept in synch with the CVS sources by
Matthew Ogilvie)
can be found on
http://sourceforge.net/tracker/index.php?func=detail&aid=822306&group_id=20011&atid=320011
Or: The "patches" link under
http://sourceforge.net/projects/cvsenhancements/
There are multiple versions of the patch on that page; please make
sure you download the latest one (21feb2004).

Actually, Derek Price is currently working on incorporating it in the
mainstream CVS.

Paul Gelderblom.




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

RE: locking a file exclusively

[Aditya Gandhi]

You may also want to look at the admin -l and admin -u commands.. 
In CVSNT these commands have been deprecated however in regular CVS I
think they are still supported. 

They should be able to help you lock and unlock files..

Regards
- Aditya Gandhi

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:info-cvs-
  [EMAIL PROTECTED] On Behalf Of Mark D. Baushke
  Sent: Wednesday, March 31, 2004 12:58 PM
  To: Sandhya
  Cc: [EMAIL PROTECTED]
  Subject: Re: locking a file exclusively
  
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
  
  Sandhya <[EMAIL PROTECTED]> writes:
  
  > I was just wondering if we could lock a file exclusively so that
  > others cannot edit that file.
  
  All users will have full control over all files in their checked out
  tree. Even if cvs initially provides read-only permissions to a given
  file, the users may still change those permissions and modify the
file.
  
  If you mean that you do not want to allow other than a particular user
  to commit change to it, then that is a different question.
  
  You might also be asking about 'cvs edit' and 'cvs watch'
functionality
  that provide advisory locks. Those locks are not strict and may be
  ignored by users.
  
  Depending on the nature of the particular file or files that are to be
  locked, you might write your commitinfo script reject any user attempt
  to commit changes to that file by anyone other than a particular user
or
  set of users you have specified.
  
  Failing that, there are various patches that try to implement strict
  locking on top of cvs floating around out there, a search for "cvs
edit
  - -c" might turn up Noel Yap's patches... I have not looked at them in
a
  long time... once upon a time there was an rcvs sourceforge.net
project,
  but I can't seem to find it this evening.
  
  If that is not good enough, I would recommend you look around and
  consider using another system for your source control. One that
provides
  reserved strict locking.
  
Good luck,
-- Mark
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.2.3 (FreeBSD)
  
  iD8DBQFAanLn3x41pRYZE/gRAjzIAKC7ciODTQUlfWNciUoniviGr3wwSwCg12Rn
  zWKMPdW9nHYkmqdT6sW6a5M=
  =5P7N
  -END PGP SIGNATURE-
  
  
  ___
  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

removal of branch

[Ramanuj Singh]

Title: removal of branch





How can we remove branch from a project



The information transmitted is intended only for the person or entity to whom it is addressed and may contain confidential and / or privileged Material. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Thank you for your understanding & co-operation. 



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