pkgsrc/devel/monotone-server/PLIST

@comment $NetBSD: PLIST,v 1.7 2014/03/11 14:05:01 jperkin Exp $
man/man7/monotone-server.7
share/examples/monotone-server/monotonerc
share/examples/monotone-server/read-permissions
share/examples/monotone-server/write-permissions
Remove example rc.d scripts from PLISTs. These are now handled dynamically if INIT_SYSTEM is set to "rc.d", or ignored otherwise. 2014-03-11 15:04:57 +01:00			`@comment $NetBSD: PLIST,v 1.7 2014/03/11 14:05:01 jperkin Exp $`
Full rewrite of the monotone-server package: - Delete the monotone-server-init script. - Modify the monotone rc.d(8) script to provide extra commands such as 'init', 'genkey' and 'read' to manipulate the server. These are not interactive, but allow the same level of customization as the previous script. Inspired by how the monotone init.d script from Fedora works. - Delete the need of an rc.conf script in the pkg_sysconfdir of this package. The settings previously stored there are now automatically discovered. - Fully automated creation of a server key: no more need to create a passphrase by hand, memorize it, and stick it on a configuration file to never look at it again. - The log file is now placed where it belongs: in varbase/log. - Addition of a monotone-server(7) manpage explaining the whole setup process and pointers to the server files. Note: upgrading from a previous version of the package will require manual intervention if the rc.d script in /etc/rc.d is replaced. However, I really doubt anyone is using this package so I didn't want to go through the trouble of implementing a migration procedure. I've added a note to the MESSAGE, though, asking users to contact me if required. 2010-03-12 10:27:17 +01:00			`man/man7/monotone-server.7`
			`share/examples/monotone-server/monotonerc`
Adapt to recent changes in monotone as the current package does not work appropriately otherwise. - The server keypair is now stored and read from ${PKG_SYSCONFDIR}/keys instead of being inside the database. - Provide and use two files (read-permissions and write-permissions) to set up netsync's access control. - During monotone-server-init, run monotone under the unprivileged user so that it creates files in the correct places (if any). - Add a note to monotone-server-init to let the user ensure that the UID and GID are correct. (I always get them wrong otherwise.) - Make the rc.d script print a "divisory" line in the log file so that different sections are easy to distinguish. Bump PKGREVISION to 2. 2006-02-21 17:09:16 +01:00			`share/examples/monotone-server/read-permissions`
			`share/examples/monotone-server/write-permissions`