pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2014-01-27	Do not set FETCH_USING, should not be set in a package Makefile.	wiz	1	-5/+1

2013-10-18	Fix a common mistake in many different packages: POSIX says that when using	bsiegert	1	-2/+3
	pax -rw, the destination directory must exist. pax in NetBSD creates it if not, pax in MirBSD complains. I read through all pkgsrc Makefiles that use pax and added an entry to INSTALLATION_DIRS, or an INSTALL_DATA_DIR invocation. I did not test all the changes but they should be fairly safe. If you notice any breakage because of this change, please contact me.
2013-09-26	Update to 3.5.2	ryoon	2	-7/+6
	Changelog: 2013-07-10 v3.5.2 allow ENV vars to be set from repo options, for use in triggers and hooks bug-fix: the new set-default-roles feature was being invoked on every run of "perms" and overriding it!
2013-09-09	Finish git rename from scmgit to git.	wiz	1	-3/+3

2013-06-11	Update to 3.5.1	ryoon	3	-8/+9
	Changelog: 2013-03-24 v3.5 (2 minor backward compat breakages) 1. 'DEFAULT_ROLE_PERMS' replaced by per repo 'default.roles' option 2. 'gitolite list-memberships' now requires a '-r' or a '-u' flag new 'gitolite owns' command (thanks to Kevin Pulo)
2013-05-31	Bump all packages for perl-5.18, that	wiz	1	-2/+2
	a) refer 'perl' in their Makefile, or b) have a directory name of p5-, or c) have any dependency on any p5- package Like last time, where this caused no complaints.
2013-03-16	One more PERL5 SUBST.	ryoon	1	-2/+2
	Ride previous revbump.
2013-03-16	* Remove unused SUBST_*.	ryoon	1	-13/+7
	* Whitespaces to tabs.
2013-03-16	Bump PKGREVISION.	ryoon	1	-2/+9
	* Fix perl's path in hook files. Fix functionality on unprivileged bootstrap pkgsrc environment.
2013-03-14	Update to 3.4	ryoon	3	-7/+8
	Changelog: 2013-03-05 v3.4 new rc file format makes it much easier to enable specific features
2013-03-02	Update to 3.3	ryoon	3	-10/+23
	Changelog: 2012-12-29 v3.3 bug fix: gl-perms propagation to slaves broke sometime after v3.2 (so if you're only picking up tagged releases you're OK) the "D" command now allows rm/unlock to be totally disabled new trigger: update-gitweb-daemon-from-options; another way to update gitweb and daemon access lists new 'create' command for explicit wild repo creation, and new AutoCreate trigger to control auto-creation allow simple macros in conf file 2012-11-14 v3.2 major efficiency boost for large setups optional support for multi-line pubkeys; see src/triggers/post-compile/ssh-authkeys-split bug fix for not creating gl-conf when repo para has only config lines and no access rules new 'bg' trigger command to put long jobs started from a trigger into background %GL_REPO and %GL_CREATOR now work for 'option's also test suite now much more BSD friendly 2012-10-05 v3.1 (security) fix path traversal on wild repos new %GL_CREATOR variable for git-config lines rsync command to create and send bundles automagically migrated 'who-pushed' logical expressions on refexes!!!
2013-01-31	* Fix typo in MESSAGE.	ryoon	4	-79/+3
	* Remove obsolete patches and regen distinfo.
2013-01-25	Update to 3.04	ryoon	4	-58/+131
	* Update MESSAGE. Changelog: * Re-written from scratch, this is gilolite g3.
2012-10-31	Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.	asau	1	-3/+1

2012-10-03	Bump all packages that use perl, or depend on a p5-* package, or	wiz	1	-1/+2
	are called p5-*. I hope that's all of them.
2012-02-13	Derive gitolite's PKGNAME from its DISTNAME.	minskim	1	-2/+2

2011-11-20	Import gitolite-2.2 as devel/gitolite	ryoon	7	-0/+204
	Gitolite is an SSH-based gatekeeper providing access control for a server that hosts many git repositories. Without gitolite, each developer needing to push to one of the repositories hosted would need a user account on that server; gitolite lets you do that just using SSH public keys tied to a single, common, user that hosts all the repositories. Gitolite can restrict who can read (clone/fetch) from or write (push) to a repository, and who can push to what branch or tag - an important issue in corporate environments. Other features include: * access control by branch-name or by modified file/directory; * per-developer "personal namespace" prefixes; * simple but powerful configuration file syntax (with validation); * config files (and authority for maintaining them) can be split; * easy integration with gitweb; * comprehensive logging; * easy migration from gitosis.