upgrade-all with current package state or above?

[Christian Weiske]

Hi all,


How do I do "pear upgrade-all" and upgrade *all* packages with new releases in the stability of the current installed version or more stable?

Currently, only preferred_state is used to decide which packages are upgraded.
I'd like to see the following:

installed: pck1-1.2.3 (stable)
available: pck1-1.2.4 (stable)
available: pck1-1.3.0b2 (beta)
-> stable 1.2.4 gets installed

installed: pck2-0.2.3 (beta)
available: pck1-0.2.4 (beta)
-> beta 0.2.4 gets installed, since the current version is also beta
--
Viele Grüße
Christian Weiske

E-Mail: ***@netresearch.de

Dipl.-Inf. Christian Weiske
Netresearch GmbH & Co. KG
-----------------------------------------------
Nonnenstraße 11d - 04229 Leipzig
Telefon: [phone] - 16
Telefax: (0341) 47 842 - 29
-----------------------------------------------
http://www.netresearch.de - ***@netresearch.de
http://www.panomic.de

++++++++++++++
Netresearch - die TYPO3 Spezialagentur


++++++++++++++
10 Jahre Netresearch - http://www.netresearch.de/10jahre

-----------------------------------------------
Registergericht:
Amtsgericht Stendal HRA 32529

Komplementär:
Netresearch Beteiligungs GmbH, Amtsgericht Leipzig HRB 17018

Geschäftsführer:
Michael Ablass, Thomas Fleck

[Christian Weiske]

Anyone?

Post by Christian Weiske
How do I do "pear upgrade-all" and upgrade *all* packages with new
releases in the stability of the current installed version or more
stable?
Currently, only preferred_state is used to decide which packages are
installed: pck1-1.2.3 (stable)
available: pck1-1.2.4 (stable)
available: pck1-1.3.0b2 (beta)
-> stable 1.2.4 gets installed
installed: pck2-0.2.3 (beta)
available: pck1-0.2.4 (beta)
-> beta 0.2.4 gets installed, since the current version is also beta

[Brett Bieber]

Post by Christian Weiske
Hi all,
How do I do "pear upgrade-all" and upgrade *all* packages with new releases in the stability of the current installed version or more stable?
Currently, only preferred_state is used to decide which packages are upgraded.

I think this makes sense. Forces you to do some extra action to
install a package outside your preferred state. But, if you've
installed it already, maybe a notice if the installer sees it
available?

pear upgrade-all
Newer package channel/pck1-0.2.4 (beta) is available, but does not
match your preferred state.
Use pear upgrade channel/pck1-0.2.4 to upgrade.