Re: Re: PEAR as a distribution system
| From: | Greg Beaver | Date: | Fri, 28 Nov 2003 20:18:08 +0000 |
| Subject: | Re: Re: PEAR as a distribution system | ||
| References: | 1 2 3 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-9213@lists.php.net to get a copy of this message | ||
Christian,
I got into development on the PEAR core through a very similar kind of question. I basically asked "why can't PEAR do ______?" and when there was no answer, I coded a solution. I think you will find that should you do the same, it would be seriously considered for inclusion. Of course, if you don't have time or interest in this, then perhaps PEAR is not yet ready for what you need.
However, the best way to do what you want to do is to use the --force directive of
pear install --force Package.tgz
The revert command I wrote is designed to work with a PEAR-style server. Fortunately, when channels are introduced, you'll be able to distribute your application through just such a custom server and have the full benefit of revert.
Incidentally, revert will be in 1.4, just waiting for 1.3 final to come out before I commit my code to CVS.
Greg
Christian Joergensen wrote:
On Fri, 2003-11-28 at 12:54, Michael Wallner wrote:What about a local cache archive? (just as Debian's APT has)but if I somehow get a broken package distributed, is there then an easy way to do a rollback?Some time ago Greg brought up a discussion/idea about a "revert" command, but AFAIK this will only work with a kinda intelligent server part like the PEAR server with XML-RPC interface, so the installer can retrieve the prior installed version easiliy...