Date: Wed, 2 Dec 1998 16:03:42 -0700 From: Nate Williams <nate@mt.sri.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Nate Williams <nate@mt.sri.com>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: proposal: simple cvs mod to handle shared checked-out source trees Message-ID: <199812022303.QAA09143@mt.sri.com> In-Reply-To: <199812022258.OAA19488@apollo.backplane.com> References: <199812022200.OAA19221@apollo.backplane.com> <199812022209.PAA08774@mt.sri.com> <199812022258.OAA19488@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> :I do. It's a very site-specific change that can easily be worked around > :by providing a wrapper for cvs for the shared folks. > : > :#!/bin/sh > :umask 000 > :/usr/local/bin/cvs > : > :The CVS program is complex enough already, and I'm 99.9% sure the CVS > :maintainers would never accept a feature such as this when it's so easy > :to work-around. > : > :Nate > > Well, I generally do not consider that sort of wrapper to be a > reasonable permanent solution, especially in a multi-user > environment. How is any different than having a 'different' cvs binary? > We have 20+ people who need modify-access to various company-wide > configuration files. If I replace /usr/bin/cvs with a wrapper I screw > up some of the traditional source projects (where we don't want relaxed > group perms). Ok, write a wrapper that checks for -g, and then have it relax the permissions. Again, this is a very site-specific change that shouldn't go into FreeBSD, IMO. > I use shell wrappers for relatively complex things, like getting JDK's > to work or supporting multiple JDK revs on a single system (which you need > to do if you want to write & test Java that is browser-compatible), but > things are a whole lot more clean when a commonly used (or potentially > commonly used) feature can be integrated into a program. Commonly used at your site, but very rarely (if at all) used at other sites. The 'CVS' way of doing thing is to have each developer check out their own copy of things, not to have a shared repository. > In this case, cvs already does chmod munging when dealing with > the backend archive to handle shared CVS repositories. ???? What do you mean by 'shared CVS repositories'? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812022303.QAA09143>