svn::hooks::denyfilenames(3pm) [debian man page]

SVN::Hooks::DenyFilenames(3pm)				User Contributed Perl Documentation			    SVN::Hooks::DenyFilenames(3pm)

NAME

       SVN::Hooks::DenyFilenames - Deny some file names.

VERSION

       version 1.19

SYNOPSIS

       This SVN::Hooks plugin is used to disallow the addition of some file names.

       It's active in the "pre-commit" hook.

       It's configured by the following directives.

   DENY_FILENAMES(REGEXP, [REGEXP => MESSAGE], ...)
       This directive denies the addition of new files matching the Regexps passed as arguments. If any file or directory added in the commit
       matches one of the specified Regexps the commit is aborted with an error message telling about every denied file.

       The arguments may be compiled Regexps or two-element arrays consisting of a compiled Regexp and a specific error message. If a file matches
       one of the lone Regexps an error message like this is produced:

	       DENY_FILENAMES: filename not allowed: filename

       If a file matches a Regexp associated with an error message, the specified error message is substituted for the 'filename not allowed'
       default.

       Note that this directive specifies a default restriction. If there are any DENY_FILENAMES_PER_PATH directives (see below) being used, this
       one is only used for files that don't match any specific rules there.

       Example:

	       DENY_FILENAMES(
		   qr/.(doc|xls|ppt)$/i, # ODF only, please
		   [qr/.(exe|zip|jar)/i => 'No binaries, please!'],
	       );

   DENY_FILENAMES_PER_PATH(REGEXP => REGEXP, REGEXP => [REGEXP => MESSAGE], ...)
       This directive is more specific than the DENY_FILENAMES, because it allows one to specify different restrictions in different regions of
       the repository tree.

       Its arguments are a sequence of rules, each one consisting of a pair. The first element of each pair is a regular expression specifying
       where in the repository this rule applies. It applies if any file being added matches the regexp. The second element specifies the
       restrictions that should be imposed, just like the arguments to DENY_FILENAMES.

       The first rule matching an added file is used to check it. The following rules aren't tried.

       Only if no rules match a particular file will the restrictions defined by DENY_FILENAMES be imposed.

       Example:

	       DENY_FILENAMES_PER_PATH(
		   qr:/src/:   => [qr/[^w.-]/ => 'source files must be strict'],
		   qr:/doc/:   => qr/[^ws.-]/i, # document files allow spaces too.
		   qr:/notes/: => qr/^$/,	  # notes directory allows anything.
	       );

AUTHOR

       Gustavo L. de M. Chaves <gnustavo@cpan.org>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2012 by CPqD.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.14.2							    2012-06-24					    SVN::Hooks::DenyFilenames(3pm)

SVN::Hooks::UpdateConfFile(3pm) 			User Contributed Perl Documentation			   SVN::Hooks::UpdateConfFile(3pm)

NAME

       SVN::Hooks::UpdateConfFile - Maintain the repository configuration versioned.

VERSION

       version 1.19

SYNOPSIS

       This SVN::Hooks plugin allows you to maintain the repository configuration files under version control.

       The repository configuration is usually kept in the directory "conf" under the directory where the repository was created. In a brand new
       repository you see there the files "authz", "passwd", and "svnserve.conf". It's too bad that these important files are usually kept out of
       any version control system. This plugin tries to solve this problem allowing you to keep these files versioned under the same repository
       where they are used.

       It's active in the "pre-commit" and the "post-commit" hooks.

       It's configured by the following directive.

   UPDATE_CONF_FILE(FROM, TO, @ARGS)
       This directive tells that after a successful commit the file FROM, kept under version control, must be copied to TO.

       FROM can be a string or a qr/Regexp/ specifying the file path relative to the repository's root (e.g. "trunk/src/version.c" or
       "qr:^conf/(w+).conf$:").

       TO is a path relative to the "/repo/conf" directory in the server. It can be an explicit file name or a directory, in which case the
       basename of FROM is used as the name of the destination file.

       If FROM is a qr/Regexp/, TO is evaluated as a string in order to allow for the interpolation of capture buffers from the regular
       expression. This is useful to map the copy operation to a diferent directory structure. For example, this configuration
       "qr:^conf/(w+).conf$: => '$1.conf'" updates any .conf file in the repository conf directory.

       The optional @ARGS must be a sequence of pairs like these:

       validator => ARRAY or CODE
	   A validator is a function or a command (specified by an array of strings that will be passed to the shell) that will check the contents
	   of FROM in the pre-commit hook to see if it's valid. If there is no validator, the contents are considered valid.

	   The function receives three arguments:

	   A string with the contents of FROM
	   A string with the relative path to FROM in the repository
	   An SVN::Look object representing the commit transaction

	   The command is called with three arguments:

	   The path to a temporary copy of FROM
	   The relative path to FROM in the repository
	   The path to the root of the repository in the server
       generator => ARRAY or CODE
	   A generator is a function or a command (specified by an array of strings that will be passed to the shell) that will transform the
	   contents of FROM in the post-commit hook before copying it to TO. If there is no generator, the contents are copied as is.

	   The function receives the same three arguments as the validator's function above.

	   The command is called with the same three arguments as the validator's command above.

       actuator => ARRAY or CODE
	   An actuator is a function or a command (specified by an array of strings that will be passed to the shell) that will be invoked after a
	   successful commit of FROM in the post-commit hook.

	   The function receives the same three arguments as the validator's function above.

	   The command is called with the same three arguments as the validator's command above.

       rotate => NUMBER
	   By default, after each successful commit the TO file is overwriten by the new contents of FROM. With this option, the last NUMBER
	   versions of TO are kept on disk with numeric suffixes ranging from .0 to ".NUMBER-1". This can be useful, for instance, in case you
	   manage to commit a wrong authz file that denies any subsequent commit.

	       UPDATE_CONF_FILE(
		   'conf/authz' => 'authz',
		   validator	=> ['/usr/local/bin/svnauthcheck'],
		   generator	=> ['/usr/local/bin/authz-expand-includes'],
		   actuator	=> ['/usr/local/bin/notify-auth-change'],
		   rotate	=> 2,
	       );

	       UPDATE_CONF_FILE(
		   'conf/svn-hooks.conf' => 'svn-hooks.conf',
		   validator	=> [qw(/usr/bin/perl -c)],
		   actuator	=> sub {
				       my ($contents, $file) = @_;
				       die "Can't use Gustavo here." if $contents =~ /gustavo/;
				   },
		   rotate	=> 2,
	       );

	       UPDATE_CONF_FILE(
		   qr:/file(
+)$:' => 'subdir/$1/file',
		   rotate	=> 2,
	       );

AUTHOR

       Gustavo L. de M. Chaves <gnustavo@cpan.org>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2012 by CPqD.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.14.2							    2012-06-24					   SVN::Hooks::UpdateConfFile(3pm)