Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7392 - Changelog visible through archlinux.org/packages interface

Attached to Project: Arch Linux
Opened by Greg (dolby) - Friday, 08 June 2007, 11:34 GMT
Last edited by eliott (cactus) - Wednesday, 13 February 2008, 22:18 GMT
Task Type Feature Request
Category Web Sites
Status Closed
Assigned To Simo Leone (neotuli)
eliott (cactus)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

that feature is awesome. thanks to pacman devs who made it true. i was wondering if the contents of the changelog file could be viewable thru the website interface. printed below/above the pkgbuild contents as i find more usefull to know the changes made to a pkg before already having it installed.
This task depends upon

Closed by  eliott (cactus)
Wednesday, 13 February 2008, 22:18 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Won't implement..for now.
Comment by Simo Leone (neotuli) - Wednesday, 13 February 2008, 18:40 GMT
I thikn the page becomes somewhat complex if it's always just printed on there. Perhaps a link or something would work better.

Implementation notes:
- db-* scripts need changes to insert changelogs into db
- db schema/django models need to change
- url? ... http://archlinux.org/packages/$pkgid/changelog
Comment by Greg (dolby) - Wednesday, 13 February 2008, 19:48 GMT
IIRC i wrote this when the Changelog was first introduced into pacman. Since an included Changelog isnt the standard behaviour for all packages i dont think this is needed to be implemented now. Maybe in the future. Near future or not, only time can tell
Comment by eliott (cactus) - Wednesday, 13 February 2008, 22:18 GMT
I agree.
I think we will close this as "wont implement" for now.
We can always revisit the issue later if/when there is better coverage for changelogs.

Loading...