Latest releases of pear_command_packaging

PEAR_Command_Packaging 0.3.0

2012年04月07日T22:51:23-05:00

QA release

Bug #17104 Fatal error: Call to undefined function cleanall()

Bug #17773 Patch: avoid using ereg

Bug #19014 remove error_reporting (for PEAR QA team)

Request #19299 Handle max + exclude version

PEAR_Command_Packaging 0.2.0

2009年06月27日T23:15:15-05:00

- fix Bug #9932: cannot build specs from external channels [cellog]
- fix Bug #10116: fatal error when packaging packages from other channel [cellog]
- NEW: Can now build specs for channels as well as packages
- Can now build specs for packages from channels other than pear.php.net (bug #9932, bug #10116, bug #10254)
- @possible_channel@ now doesn't include a trailing slash (template.spec changed to accommodate)
- @possible_channel@ is now filled even if channel is pecl.php.net/pear.php.net - this is part of moving towards a less pear.php.net-centric system where the core PEAR channels are not particularly "special"
- Add the following macros:
- @php_files_statement@
- @test_files_statement@
- @data_files_statement@
- @script_files_statement@
- @customrole_files_statement@
- @cfg_files_statement@
- @www_files_statement@
All of these are "intelligent" in that they are empty if no files of the given type exist, plus if files do exist and are in a subdirectory dedicated to the package being RPM-ified, then make-rpm-spec will just put the top level directory in the substitution, rather than a complete file list - this makes for much shorter specs in some cases. Use of the @XXX_files_statement@ substitutions is encouraged in favour of the @files@ substitution.
- Deprecate @rpm_xml_dir@ macro - this is pointless (replaced with actual path in the template specs)
- Deprecate @arch@ macro - this gave invalid results; it should either be "noarch" or not defined, not the architecture of the machine building the spec file. Replaced by @arch_statement@ if you really want to use it, although the building of specs for compiled packages (i.e. PECL) is not supported at the moment, even though in theory it should work in a similar way.
- Fix a bug if PEAR/PackageFile.php was already included
- Fix bug #10327, bug #8630 - file prefixes sometimes generated incorrectly, stops some packages building
- Add $_spec_line_format config option to allow distributors to tune the format that additional RPM headers are added to the spec in, to match their conventions
- Internal refactoring/cleanup
- Require PHP 4.3.0+ to avoid internal cruft
- Tidy summaries (trim and remove trailing dots)

PEAR_Command_Packaging 0.1.2

2006年06月28日T10:11:54-05:00

- Fix critical bug which sometimes inhibited the use of some PEAR internal commands upon installation of PEAR_Command_Packaging

PEAR_Command_Packaging 0.1.1

2006年05月17日T17:36:38-05:00

- Add support for generation of external deps (e.g. PHP extensions) (bug #6971)
- Add %l (lowercased package name) option to RPM pkgname/depname format strings
- Add support for customising the output specfile filename via the $_rpm_specname_format variable
- Make it super-easy for downstream distros to customise the various package/dep/specfile naming to suit their conventions: all the options are now grouped together in the source
- Add release_state macro for use in spec templates if required
- De-duplicate dependencies (bug #6963)
- Remove a last remaining case of hardcoded "PEAR::" package naming (when generating deps on PEAR itself)
- Improve/tidy up docfile handling (bug #7118)
- Revert PEAR package dependency to 1.4.3 and encode the 1.4.7 dep in the included template.spec instead.
- Remove some forced 'rm's in template spec file to avoid masking problems
- Abstract XML directory in default template spec
- Stop owning / in RPM packages (bug #7129)
- Wordwrap package description

PEAR_Command_Packaging 0.1.0

2006年02月28日T11:33:44-05:00

Initial release