I agree. Pacman is a good package management system as it is. It is not logical to extend the uses of pacman away from it's primary job, since this will only increase it's size and features through time. Bloateritis should be nipped in the bud; prevention is better than cure. And for those users who wish to know the cvs changes, set up a (automated?) cvs mailing list or something. The majority of the users really don't need this, and again, it's not the job of the package manager. If someone /really/ needs to know the reasons, they should either mail the packager or (preferably) check out the cvs commit mailing list archives. On the other hand, it can be argued that adding such a thing is only some text, and could be put in an array (like depends) and it could be made possible to view this explanation for upgrade through 'pacman -Qi'.
ravster.
J�rgen H�tzel wrote:
Compared to RPM, Pacman is pgk-management without bells and whistles. There are a lot nice-to-have features people will request. But to keep Pacman small and beautiful and the whole system flexible all those features should be implemented outside of pacman if possible.
There a lot of options:
* cvs commit mailing list * rss feed
J�rgen
signature.asc
Description: OpenPGP digital signature
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
