Re: [PEPr] Comment on PEAR::PEAR_PackageUpdate
| From: | Laurent Laville | Date: | Tue, 14 Mar 2006 19:54:18 +0000 |
| Subject: | Re: [PEPr] Comment on PEAR::PEAR_PackageUpdate | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-41784@lists.php.net to get a copy of this message | ||
Here are some answers for Scott, but also Christian Weiske and Justin Patrin who asked two days ago why i've deleted my proposal about a frontend for PEAR_PackageFileManager2.
I've talked with Scott about a common solution for my web frontend and its own Gtk2 frontend : a backend as for PPU.
This class is almost finished, and before to propose it officially to the PEAR community with a revisited copy of my old web frontend, i'll
test it with Scott.
BTW i open NOW a call for comment about a CLI frontend for future PEAR_PackageFileManager2. Do you think its possible ? does anyone have already ideas ? All feedback are welcome !!!
Scott, i'll send to you a preview of PFM backend with a PEAR_ErrorStack implementation, i've used. Something very similar to your PPU need.
I've also used a contribution (not official) part of code of StackThunk package from Ian Eure. I hope it won't be a problem if i use part of code: especially PEAR_Error repackaging. And of course give a credit to Ian.
Laurent Laville
PS: Greg Beaver, if you read this post, i'm still waiting a answer about my help request from PFM package 2.0 and install conditions.
Scott Mattocks a écrit :
Thanks for the comments Justin, Justin Patrin wrote:I would suggest using PEAR_ErrorStack instead of implementing your own error stack in the class.I am thoroughly confused by the docs for PEAR_ErrorStack but I will try to read them over again and update the package.