| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 1.10.16 |
| Bug #15242 | Allow unpacking, patching and installing a PEAR package | ||
|---|---|---|---|
| Submitted: | 2008-12-05 08:20 UTC | ||
| From: | wrobel | Assigned: | |
| Status: | Bogus | Package: | PEAR (version 1.7.2) |
| PHP Version: | 5.2.6 | OS: | |
| Roadmaps: | (Not assigned) | ||
[2008-12-05 08:20 UTC] wrobel
(Gunnar Wrobel)
Description:
------------
PEAR directly installs released packages from a tgz. These tgz's are only installable as a package and not when unpacked. This prevents patching a package.
As packers we would like to be able to
1) Download a package
2) Unpack it
3) Patch it
4) Install the unpackaged, patched code so that the installation includes the patches.
See also https://www.intevation.de/roundup/kolab/issue3294
Comments
[2008-12-05 16:37 UTC] saltybeagle
(Brett Bieber)
You can install by using:
1) Download a package
2) Unpack it
3) Patch it
4) Use pear install package.xml to install the unpackaged, patched code so that the installation includes the patches.
The only thing out of the ordinary is that the package.xml should be in the directory extracted for the tar files.
[2008-12-05 17:07 UTC] wrobel
(Gunnar Wrobel)
What about the md5sums in the package.xml from the tgz? They don't have to be adapted to the new values for the patched files? I know that is something one can also do (in fact one of the workarounds we use) but I think this makes patching more complex than it should be.
[2008-12-05 17:13 UTC] cellog
(Greg Beaver)
as you just said, you can unpack, clear the md5sum or set it to the new value in package.xml and install, there's no bug here.
[2008-12-05 18:49 UTC] wrobel
(Gunnar Wrobel)
If you look at the packaging systems available for C, Perl, Python, Java and Ruby you will find that no such additional step is necessary for patching released code pacakges.
A packaging system is a convenience factor with the intention to make installation of code easy. Anything that removes convenience for that process is a bug in my eyes.
[2008-12-05 22:23 UTC] saltybeagle
(Brett Bieber)
"What about the md5sums in the package.xml from the tgz? They don't have to be adapted to the new values for the patched files? … I think this makes patching more complex than it should be."
MD5 sums for the files are optional, so they may or may not exist depending on the package you're installing. Your statement about it being more complex is correct, but your complaint is misdirected - the md5 is there to verify the integrity of the release, which you've just modified. Of course the installer will complain that the values do not match.
There are quite a few ways to get around your issue. I would send your patches to upstream, investigate how the individual package is built and re-create it yourself, or use the plethora of tools available to create a your custom package.xml for your modified package if you intend to use the PEAR installer to install it.