RE: [PEAR-DEV] [QA] pear install Date

Zitat von Lukas Smith <smith@backendmedia.com>: > > From: Joseph Lee [mailto:joelee@joeworks.com] > > Sent: Wednesday, July 30, 2003 11:35 AM > > > We have found out putting 'pear upgrade-all' on our Production Servers > > cron task is a silly thing to do. :( > > > > When we 'pear upgrade-all' or 'pear install Date' on our Production > > Servers, it upgrades an incomplete version of Date 1.3.1beta, missing > > "Span.php". We have to copy "Span.php" manually from CVS to each of > the > > Servers. Can one of the Date maintainers please fix this? > > > > Is there a way I can get "pear upgrade-all" to only upgrade "stable" > > versions? > > This is very bad thing to do in any case. > We are working on making the pear installer a bit more fool proof. > Especially we are also addressing the issue that a new major release can > always break BC as well. > > I would never ever change my libs with a cron job. "Don't fix it if it > aint broken" is the rule you want to follow. But that doesn't change the fact that there is a broken (in the sense of "unusable") package available that the PEAR group wasn't able to fix for TWO months although the fix was applied a few days after the release to CVS. How do you expect developers to depend on PEAR packages if they suddenly disappear, break BC, change the meaning or simply stop to work? The consequence will be that we start to develop everything on our own again instead of relying on a central "high quality" repository. Jan. -- http://www.horde.org - The Horde Project http://www.ammma.de - discover your knowledge http://www.tip4all.de - Deine private Tippgemeinschaft