pkgsrc/sysutils/ruby-syslog-logger/PLIST

@comment $NetBSD: PLIST,v 1.2 2018/01/01 18:33:33 rillig Exp $
${GEM_HOME}/cache/${GEM_NAME}.gem
${GEM_LIBDIR}/README.rdoc
${GEM_LIBDIR}/lib/syslog-formatter.rb
${GEM_LIBDIR}/lib/syslog-logger.rb
${GEM_LIBDIR}/test/test_syslog_logger.rb
${GEM_HOME}/specifications/${GEM_NAME}.gemspec
Cleaned up PLIST files. The actual cleanup has been done by pkglint: * Added missing identifier comments * Replaced ${PKGMANDIR} with a simple man, since the infrastructure does all the magic for PLISTs 2018-01-01 19:33:32 +01:00			`@comment $NetBSD: PLIST,v 1.2 2018/01/01 18:33:33 rillig Exp $`
Add ruby-syslog-logger package version 1.6.8. Logger::Syslog is a Logger replacement that logs to syslog. It is almost drop-in with a few caveats. You can add Logger::Syslog to your Rails production environment to aggregate logs between multiple machines. NOTE! You can only set the Logger::Syslog program name and facility when you initialize Logger::Syslog for the first time. This is a limitation of the way Logger::Syslog uses syslog (and in some ways, a limitation of the way syslog(3) works). Attempts to change Logger::Syslog's program name or facility after the first initialization will be ignored. This particular Logger::Syslog improves the original by correctly mapping Rails log severities to the Syslog counterparts. It also adds the ability to select a syslog facility other than "user." 2017-06-10 18:08:06 +02:00			`${GEM_HOME}/cache/${GEM_NAME}.gem`
			`${GEM_LIBDIR}/README.rdoc`
			`${GEM_LIBDIR}/lib/syslog-formatter.rb`
			`${GEM_LIBDIR}/lib/syslog-logger.rb`
			`${GEM_LIBDIR}/test/test_syslog_logger.rb`
			`${GEM_HOME}/specifications/${GEM_NAME}.gemspec`