Re: Automatic changelog display?
| From: | Tomas V.V.Cox | Date: | Fri, 19 Sep 2003 15:22:00 +0000 |
| Subject: | Re: Automatic changelog display? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21780@lists.php.net to get a copy of this message | ||
You just need to go to the package home for getting this info, both
the changelog and the bugs. The PEAR installer TODO list has grow
enough for a year of working, including: PECL binaries, channels,
subpackages, api generation, dtd validation, applications, among
others, so please don't ask and ask for stuff but help (or well put
some funds ;).
Tomas V.V.Cox
On Friday, September 19, 2003 14:19, Stefan Neufeind wrote:
> Hi,
> Alexey noted that users "*should* read changelogs before upgrading".
> An interesting point. How about the idea of having a way to display
> the partial changelog between the currently installed version and the
> latest version via the pear-installer? In interactive tools this
> could be used, right?
> Something like:
> pear list-upgrades
=>> e.g. DB 1.5 1.6
> pear retrieve-upgrade-changelog DB
=>> [partial changelog for this version-step goes here]
> Another think might be displaying open bugs for a package if they
> might be of interest to the version to which you would like to
> upgrade. The Debian-users running testing / unstable may already be
> aware of such a thing in the apt-get installer. The package is called
> "apt-listbugs" there. So if you want to install a version for which
> open bugs exist first the bugs are displayed and you are required to
> manually confirm that you still want to install the upgrade. Maybe we
> could also allow the user to install a version below the latest, so
> he doesn't run into the bugs (if they are important).
> For sure we have to keep in mind that such "interactive" features
> don't interfer with scripts currently using the non-interactive pear-
> installer for automatic purpose.
> Stefan
--
Tomas V.V.Cox mailto:cox@idecnet.com