Re: Keeping stuff out of my repository?

Thanks, Toby,

But unfortunately, the Book says: "do not
          modify a commit transaction using hook scripts."

Essentially what I want to do is enforce the ignore list, not create more work for people importing their code base.  (I do not agree with the Book's assertion that people will learn good habits if I deny their commits -- they're more likely to just give up and email me a tarball.)

I suppose there's some kind of script I could write to continually walk the repository, or maybe use a pre hook to write a URI file of stuff to auto-delete.  Am I the only one who's ever had this issue?

Thanks,
Chris

--- On Thu, 10/30/08, Toby Thain <toby_at_telegraphics.com.au> wrote:
From: Toby Thain <toby_at_telegraphics.com.au>
Subject: Re: Keeping stuff out of my repository?
To: castonfirst_at_yahoo.com
Cc: users_at_subversion.tigris.org
Date: Thursday, October 30, 2008, 12:39 PM

On 30-Oct-08, at 12:00 PM, caston first wrote:

> I am administering a repository for a group of developers who are too lazy
to follow instructions that provide a standard value for the client-side
svn-ignore setting. As a result, I am continually removing compiler cruft from
the repo!
>
> The clients in use vary - so far just TortoiseSVN, Subclipse and the
command line client.
>
> Is there ANY way I can enforce my repository's ignore rules? I know
it's kind of a mainframe mentality but the added hassle is just driving me
insane...

You can reject commits with a pre-commit hook. See the text of
hooks/pre-commit.tmpl in any repo.

--Toby

>
>
> Thanks,
> Caston
>
Received on 2008-10-30 19:26:02 CET