summaryrefslogtreecommitdiff
path: root/devel/p5-Config-IniFiles
AgeCommit message (Collapse)AuthorFilesLines
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2005-11-07Removed the buildlink3.mkmartti1-18/+0
I got few private comments that one should not use buildlink3.mk but the standard DEPENDS statement because we do not link against libraries in this case.
2005-11-05Added buildlink3.mk for this package.martti1-0/+18
2005-08-06Bump the PKGREVISIONs of all (638) packages that hardcode the locationsjlam1-2/+2
of Perl files to deal with the perl-5.8.7 update that moved all pkgsrc-installed Perl files into the "vendor" directories.
2005-07-13Turn PERL5_PACKLIST into a relative path instead of an absolute path.jlam1-2/+2
These paths are now relative to PERL5_PACKLIST_DIR, which currently defaults to ${PERL5_SITEARCH}. There is no change to the binary packages.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests.agc1-1/+2
2004-12-20since perl is now built with threads on most platforms, the perl archlibgrant1-1/+2
module directory has changed (eg. "darwin-2level" vs. "darwin-thread-multi-2level"). binary packages of perl modules need to be distinguishable between being built against threaded perl and unthreaded perl, so bump the PKGREVISION of all perl module packages and introduce BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct dependencies are registered and the binary packages are distinct. addresses PR pkg/28619 from H. Todd Fujinaka.
2004-12-05Update p5-Config-IniFiles from version 2.23 to 2.38.he2-5/+5
Change log: Revision 2.38 2003/05/14 01:30:32 wadg - fixed RewriteConfig and ReadConfig to work with open file handles - added a test to ensure that blank files throw no warnings - added a test for error messages from malformed lines Revision 2.37 2003/01/31 23:00:35 wadg Updated t/07misc test 4 to remove warning Revision 2.36 2002/12/18 01:43:11 wadg - Improved error message when an invalid line is encountered in INI file - Fixed bug 649220; importing a non-file-based object into a file one no longer destroys the original object Revision 2.33 2002/11/12 14:48:16 grail Addresses feature request - [ 403496 ] A simple change will allow support on more platforms Revision 2.32 2002/11/12 14:15:44 grail Addresses bug - [225971] Respect Read-Only Permissions of File System Revision 2.31 2002/10/29 01:45:47 grail [ 540867 ] Add GetFileName method Revision 2.30 2002/10/15 18:51:07 wadg Patched to stopwarnings about utf8 usage. Revision 2.29 2002/08/15 21:33:58 wadg - Support for UTF Byte-Order-Mark (Raviraj Murdeshwar) - Made tests portable to Mac (p. kent) - Made file parsing portable for s390/EBCDIC, etc. (Adam Fischler) - Fixed import bug with Perl 5.8.0 (Marek Rouchal) - Fixed precedence bug in WriteConfig (Luc St Louis) - Fixed broken group detection in SetGroupMember and RemoveGroupMember (Kay Ro"pke) - Added line continuation character (/) support (Marek Rouchal) - Added configurable comment character support (Marek Rouchal) Revision 2.28 2002/07/04 03:56:05 grail Changes for resolving bug 447532 - _section::FETCH should return array ref for multiline values. Revision 2.27 2001/12/20 16:03:49 wadg - Fixed bug introduced in new valid file check where ';' comments in first lines were not considered valid - Rearranged some tests to put them in the proper files (case and -default) - Added more comment test to cover more cases - Fixed first two comments tests which weren't doing anything Revision 2.26 2001/12/19 22:20:50 wadg #481513 Recognize badly formatted files Revision 2.25 2001/12/12 20:44:48 wadg Update to bring CVS version in synch Revision 2.24 2001/12/07 10:03:06 wadg 222444 Ability to load from arbitrary source
2004-04-25Bl3ify and enable pkgviews installation.minskim1-2/+4
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2002-10-20Use buildlink2. Use perl5/module.mk.seb1-6/+3
2001-12-19Update to 2.23mjl2-5/+5
Fixed bugs 482353,233372. Updated doc for new mgr. Bug fix: multiple blank lines counted as one Added checks for method parameters being defined fixed some regexes to make them stricter Fixed greps to make them consistent through the code (also a vain attempt to help my editors do syntax colouring properly) Added AddSection method, replaced chunk of ReadConfig with AddSection Added case handling stuff to more methods Added RemoveGroupMember Made variable names more consistent through OO methods Restored Unix EOLs
2001-11-26Buildlinkify, in the sense that only the perl headers are found injlam1-3/+4
${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum3-1/+1
2001-10-18SVR4 packages have a limit of 9 chars for a package name.veego1-1/+2
The automatic truncation in gensolpkg doesn't work for packages which have the same package name for the first 5-6 chars. e.g. amanda-server and amanda-client would be named amanda and amanda. Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for amanda-server. All svr4 packages also have a vendor tag, so we have to reserve some chars for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6 or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the vendor tag enough room. All p5-* packages and a few other packages have now a SVR4_PKGNAME.
2001-08-10Initial import of p5-Config-IniFiles 2.19mjl4-0/+28
Config::IniFiles provides a way to have readable configuration files outside your Perl script. Configurations can be imported (inherited, stacked,...), sections can be grouped, and settings can be accessed from a tied hash.