kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/ruby-log4r/Makefile

22 lines
621 B
Makefile
Raw Normal View History

Comment out dead sites.
2017-09-04 20:00:49 +02:00
# $NetBSD: Makefile,v 1.8 2017/09/04 18:00:53 wiz Exp $
Initial import of ruby18-log4r-1.0.5 as devel/ruby-log4r. Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more. Log4r is an adherent to the philosophy of logging using simple print statements. What Log4r adds to this philosophy is a flexible way of controling the information being logged. Log information can be sent to any kind of destination and with varying degrees of importance. Log4r is designed so that logging statements can remain in production code with almost no extra computational cost.
2008-04-04 17:17:37 +02:00
Update ruby-log4r to 1.1.10. Exact changes are unknown.
2012-03-17 15:40:33 +01:00
DISTNAME= log4r-1.1.10
Initial import of ruby18-log4r-1.0.5 as devel/ruby-log4r. Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more. Log4r is an adherent to the philosophy of logging using simple print statements. What Log4r adds to this philosophy is a flexible way of controling the information being logged. Log information can be sent to any kind of destination and with varying degrees of importance. Log4r is designed so that logging statements can remain in production code with almost no extra computational cost.
2008-04-04 17:17:37 +02:00
CATEGORIES= devel
Comment out dead sites.
2017-09-04 20:00:49 +02:00
#HOMEPAGE= http://log4r.rubyforge.org/
Initial import of ruby18-log4r-1.0.5 as devel/ruby-log4r. Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more. Log4r is an adherent to the philosophy of logging using simple print statements. What Log4r adds to this philosophy is a flexible way of controling the information being logged. Log information can be sent to any kind of destination and with varying degrees of importance. Log4r is designed so that logging statements can remain in production code with almost no extra computational cost.
2008-04-04 17:17:37 +02:00
COMMENT= Flexible logging library
Update devel/ruby-log4r to 1.1.8. * Use lang/ruby/gem.mk instead of misc/rubygems/rubygem.mk. * Update HOMEPAGE. * Add LICENSE. Changes may be too may, please refer http://log4r.rubyforge.org/.
2010-09-10 07:54:13 +02:00
LICENSE= gnu-lgpl-v3
Initial import of ruby18-log4r-1.0.5 as devel/ruby-log4r. Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more. Log4r is an adherent to the philosophy of logging using simple print statements. What Log4r adds to this philosophy is a flexible way of controling the information being logged. Log information can be sent to any kind of destination and with varying degrees of importance. Log4r is designed so that logging statements can remain in production code with almost no extra computational cost.
2008-04-04 17:17:37 +02:00
# The log4r gem installs the RDoc files under ${GEM_LIBDIR}/doc instead of
# ${GEM_DOCDIR}, so we need to generate the dynamic PLIST entries for
# those files.
#
GENERATE_PLIST+= \
${ECHO} "@comment The following lines are automatically generated." && \
Remove @dirrm related logic.
2009-06-15 00:57:58 +02:00
cd ${DESTDIR}${PREFIX} && \
Initial import of ruby18-log4r-1.0.5 as devel/ruby-log4r. Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more. Log4r is an adherent to the philosophy of logging using simple print statements. What Log4r adds to this philosophy is a flexible way of controling the information being logged. Log information can be sent to any kind of destination and with varying degrees of importance. Log4r is designed so that logging statements can remain in production code with almost no extra computational cost.
2008-04-04 17:17:37 +02:00
${FIND} ${GEM_LIBDIR:S|${PREFIX}/||}/doc \! -type d -print | \
Fix a number of GENERATE_PLIST entries to always have a terminating ;
2009-06-16 17:25:31 +02:00
${SORT};
Initial import of ruby18-log4r-1.0.5 as devel/ruby-log4r. Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more. Log4r is an adherent to the philosophy of logging using simple print statements. What Log4r adds to this philosophy is a flexible way of controling the information being logged. Log information can be sent to any kind of destination and with varying degrees of importance. Log4r is designed so that logging statements can remain in production code with almost no extra computational cost.
2008-04-04 17:17:37 +02:00
Update devel/ruby-log4r to 1.1.8. * Use lang/ruby/gem.mk instead of misc/rubygems/rubygem.mk. * Update HOMEPAGE. * Add LICENSE. Changes may be too may, please refer http://log4r.rubyforge.org/.
2010-09-10 07:54:13 +02:00
.include "../../lang/ruby/gem.mk"
Initial import of ruby18-log4r-1.0.5 as devel/ruby-log4r. Log4r is a comprehensive and flexible logging library written in Ruby for use in Ruby programs. It features a hierarchical logging system of any number of levels, custom level names, logger inheritance, multiple output destinations, execution tracing, custom formatting, thread safteyness, XML and YAML configuration, and more. Log4r is an adherent to the philosophy of logging using simple print statements. What Log4r adds to this philosophy is a flexible way of controling the information being logged. Log information can be sent to any kind of destination and with varying degrees of importance. Log4r is designed so that logging statements can remain in production code with almost no extra computational cost.
2008-04-04 17:17:37 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink