I'm working on a solution for our BI team.
The guys create reports that are in use, when they make changes i want to version and store the earlier one.
If the new report has issues, replace this with the earlier instance.
So, i want this guys to add to source control, checkin / checkout.
But i dont want them to deleted the older instance.
The existing workaround requires people to make a copy of the report, zip it and store it for safe-keeping.
i agree, subversion is not made for this activity. I'm trying to look for a solution that is easy to setup and own.
- maheshwar> Subject: RE: Re: user with delete rights> Date: Mon, 17 Mar 2008 08:14:24 -0700> From: tgleason_at_impac.com> To: talden_at_gmail.com; maheshwars_at_hotmail.com> CC: users_at_subversion.tigris.org> > And if your repository represents source code, then such a configuration> would prevent User A from doing any significant refactoring of code> (deleting an old file in favor of a newer one, renaming files or> projects, etc.). What that is going to say to User A is that you don't> trust them and don't want them working up to their own capabilities.> > I've seen similar practices in use, and in my experience they lead to> poor quality as people avoid making the changes they know are really> needed and instead hack things together in the "old" files.> > -----Original Message-----> From: Talden [mailto:talden_at_gmail.com] > Sent: Monday, March 17, 2008 3:07 AM> To: maheshwar singh> Cc: users_at_subversion.tigris.org> Subject: Re: user with delete rights> > On Mon, Mar 17, 2008 at 5:45 PM, maheshwar singh> <maheshwars_at_hotmail.com> wrote:> > I'm using svnserver to backup and version my reports. I need to> create 2> > users -> > 1. User A - has rights to only add and update contents to the> repository> > 2. User B - has rights to delete any or all the contents in the> repository.> >> > How do i do this?> > I don't believe that there's a way, other than using pre-commit hooks,> to provide this action-oriented control - users are either excluded,> read-only, or read-write.> > That said, taking away delete in a versioned system isn't useful> anyway - though they shouldn't delete they could produce a similar> effect by checking in an empty file in place of the original. The> action to reverse this is much the same as recovering a deleted file> so I wouldn't be too concerned. If you really do want to try and> block the commit of remove (including rename then) then a pre-commit> hook is needed - it wouldn't surprise me if something is available in> the contributor content for Subversion.> > --> Talden> > ---------------------------------------------------------------------> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org> For additional commands, e-mail: users-help_at_subversion.tigris.org>
Tried the new MSN Messenger? Itís cool! Download now.
Received on 2008-03-18 12:39:00 CET