kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/p5-namespace-clean/Makefile

25 lines
818 B
Makefile
Raw Normal View History

Update 0.25 to 0.26 ------------------- 0.26 2015-10-07 17:43 (UTC) - Exclusively use Package::Stash::PP on perls < 5.8.7 until a fixed Package::Stash::XS ships - breakage keeps getting reintroduced ( RT#107343, RT#74151 ) - Explicitly document the late runtime binding of `sort SUBNAME ...` ( RT#101247 ) - No longer rely on Sub::Identify - either use Sub::Util or B ( should solve RT#96945 )
2015-11-26 14:08:28 +01:00
# $NetBSD: Makefile,v 1.22 2015/11/26 13:08:28 mef Exp $
Import p5-namespace-clean version 0.08. Keeping packages clean When you define a function, or import one, into a Perl package, it will naturally also be available as a method. This does not per se cause problems, but it can complicate subclassing and, for example, plugin classes that are included via multiple inheritance by loading them as base classes. The "namespace::clean" pragma will remove all previously declared or imported symbols at the end of the current package's compile cycle. Functions called in the package itself will still be bound by their name, but they won't show up as methods on your class or instances.
2008-07-23 00:57:04 +02:00
Update 0.25 to 0.26 ------------------- 0.26 2015-10-07 17:43 (UTC) - Exclusively use Package::Stash::PP on perls < 5.8.7 until a fixed Package::Stash::XS ships - breakage keeps getting reintroduced ( RT#107343, RT#74151 ) - Explicitly document the late runtime binding of `sort SUBNAME ...` ( RT#101247 ) - No longer rely on Sub::Identify - either use Sub::Util or B ( should solve RT#96945 )
2015-11-26 14:08:28 +01:00
DISTNAME= namespace-clean-0.26
Import p5-namespace-clean version 0.08. Keeping packages clean When you define a function, or import one, into a Perl package, it will naturally also be available as a method. This does not per se cause problems, but it can complicate subclassing and, for example, plugin classes that are included via multiple inheritance by loading them as base classes. The "namespace::clean" pragma will remove all previously declared or imported symbols at the end of the current package's compile cycle. Functions called in the package itself will still be bound by their name, but they won't show up as methods on your class or instances.
2008-07-23 00:57:04 +02:00
PKGNAME= p5-${DISTNAME}
CATEGORIES= devel perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=namespace/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://search.cpan.org/dist/namespace-clean/
COMMENT= Perl module to keep imports and functions out of your namespace
Updating devel/p5-namespace-clean from 0.11 to 0.12 pkgsrc changes: - Adding right license definition - Adjusting dependencies Upstream changes: [0.12] Thu Jan 14 03:22:03 CET 2010 - Stop relying on stash entries always being upgraded into real GVs (Zefram). - Work around $DB::sub (Yuval Kogman). - Fix restoring of non-code symbols when cleaning (Ben Morrows).
2010-01-16 19:00:36 +01:00
LICENSE= ${PERL5_LICENSE}
Import p5-namespace-clean version 0.08. Keeping packages clean When you define a function, or import one, into a Perl package, it will naturally also be available as a method. This does not per se cause problems, but it can complicate subclassing and, for example, plugin classes that are included via multiple inheritance by loading them as base classes. The "namespace::clean" pragma will remove all previously declared or imported symbols at the end of the current package's compile cycle. Functions called in the package itself will still be bound by their name, but they won't show up as methods on your class or instances.
2008-07-23 00:57:04 +02:00
Update from version 0.13 to version 0.14. Pkgsrc changes: - Not need for a compiler Upstream changes: [0.14] Thu Mar 18 11:15:38 CET 2010 - Disable auto_install. - Turn the error prone debugger test into an author test.
2010-04-18 10:44:38 +02:00
USE_LANGUAGES= # empty
Import p5-namespace-clean version 0.08. Keeping packages clean When you define a function, or import one, into a Perl package, it will naturally also be available as a method. This does not per se cause problems, but it can complicate subclassing and, for example, plugin classes that are included via multiple inheritance by loading them as base classes. The "namespace::clean" pragma will remove all previously declared or imported symbols at the end of the current package's compile cycle. Functions called in the package itself will still be bound by their name, but they won't show up as methods on your class or instances.
2008-07-23 00:57:04 +02:00
Update to 0.24 Update DEPENDS Upstream changes: [0.24] - Properly skip debugger test when optional deps not available - Make sure pure-perl tests pass correctly on space-containing paths (RT#77528) - Remove all the pure-perl fallback code and depend on PP-capable B::H::EOS 0.12
2013-05-02 08:50:42 +02:00
DEPENDS+= p5-B-Hooks-EndOfScope>=0.12:../../devel/p5-B-Hooks-EndOfScope
Updated devel/p5-namespace-clean to 0.21 [0.21] - When using the tie() fallback ensure we do not obliterate a foreign tie() - Better document how to disable the tie() fallback [0.20_01] (the "mst made me do it" release) - Only invoke the deleted sub stashing if we run udner a debugger (avoid runtime penalty of Sub::Name/Sub::Identify) - Spellfixes (RT#54388) - When B::Hooks::EndOfScope is not available, switch to a simple tie() of %^H. While it can not 100% replace B::H::EOS, it does everything n::c needs [0.20] - Bump Package::Stash dependency to 0.22 to pull in a bugfix in Package::Stash::XS 0.19. [0.19] - Port to the new Package::Stash 0.18 API and depend on it. - Don't rely on package::stash's remove_package_symbol implementation (doy).
2011-08-18 13:53:02 +02:00
DEPENDS+= p5-Package-Stash>=0.23:../../devel/p5-Package-Stash
Needs p5-Module-Implementation. Bump revision.
2013-05-06 16:42:08 +02:00
DEPENDS+= p5-Module-Implementation-[0-9]*:../../devel/p5-Module-Implementation
Updating devel/p5-namespace-clean from 0.11 to 0.12 pkgsrc changes: - Adding right license definition - Adjusting dependencies Upstream changes: [0.12] Thu Jan 14 03:22:03 CET 2010 - Stop relying on stash entries always being upgraded into real GVs (Zefram). - Work around $DB::sub (Yuval Kogman). - Fix restoring of non-code symbols when cleaning (Ben Morrows).
2010-01-16 19:00:36 +01:00
Comment out dependencies of the style {perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS since pkgsrc enforces the newest perl version anyway, so they should always pick perl, but sometimes (pkg_add) don't due to the design of the {,} syntax. No effective change for the above reason. Ok joerg
2015-07-12 20:56:06 +02:00
#BUILD_DEPENDS+= {perl>=5.10.1,p5-Test-Simple>=0.88}:../../devel/p5-Test-Simple
Import p5-namespace-clean version 0.08. Keeping packages clean When you define a function, or import one, into a Perl package, it will naturally also be available as a method. This does not per se cause problems, but it can complicate subclassing and, for example, plugin classes that are included via multiple inheritance by loading them as base classes. The "namespace::clean" pragma will remove all previously declared or imported symbols at the end of the current package's compile cycle. Functions called in the package itself will still be bound by their name, but they won't show up as methods on your class or instances.
2008-07-23 00:57:04 +02:00
PERL5_PACKLIST= auto/namespace/clean/.packlist
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink