AUR web interface

**This is the bug tracker for the AUR web interface.**

Use this tracker to report bugs or make feature requests regarding the behaviour or implementation of the AUR software.
Please read the Reporting Bug Guidelines before filing a new task.
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

- Please report bugs related to Arch Linux official packages here: http://bugs.archlinux.org/index.php?project=1
- Please report bugs for [community] packages here: http://bugs.archlinux.org/index.php?project=5
- For any packages in the AUR contact the maintainer or leave a comment on the package's detail page.

Source Code:
https://projects.archlinux.org/aurweb.git/
Tasklist

FS#10863 - Adding maintainer comment box for important updates and caveats concerning packages

Attached to Project: AUR web interface
Opened by james francis toy iv (bbs) - Tuesday, 08 July 2008, 16:42 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 15 February 2016, 18:42 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Medium
Priority Normal
Reported Version 1.5.1
Due in Version 4.2.0
Due Date Undecided
Percent Complete 100%
Votes 38
Private No

Details

AUR,
I think we should try to implement a comment box above the general comment box that can be edited ONLY by the package maintainer -- this is important for updates and information about more complex packages -- for example -- kernel26zenmm-git does not automatically have nvidia support built in and can be supplemented by the xf86-video-nvidia (i think thats the package name i'm just doing it from memory now) -- this is useful information that should not get lost in the main comments box -- i just wanted to throw this out there -- never too many documents -- especially when there are caveats -- hope everyone is well

respectfully
-jt
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Monday, 15 February 2016, 18:42 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in 4.2.0.
Comment by Callan Barrett (wizzomafizzo) - Tuesday, 30 September 2008, 04:58 GMT
I like this idea, see what I can do about it.
Comment by Ivan Yurasov (vanDake) - Friday, 13 March 2009, 12:04 GMT
I think that it may be implemented as packages changelog
Comment by Dino Krtanjek (KRTac) - Friday, 02 October 2009, 00:01 GMT
I dont know if the best sollution would be to add a second comment box. It would be better if there would be a checkbox next to the buttons that said 'Important comment' or something like that. Then That would be threated as a important comment and saved as such in the database. the prefered way to save this in the database would be to add a new column in the database comments table, name it 'important' or something, and this would act as a flag.
Comment by (Det) - Monday, 08 April 2013, 23:26 GMT Comment by (Det) - Sunday, 14 June 2015, 13:05 GMT
Actually, the .SRCINFO already sort of provides this (doesn't show up with: $ pacman -Qi), but a separate box where you could write things directly would be helpful in many cases.
Comment by Stefan Auditor (sanduhrs) - Tuesday, 11 August 2015, 12:04 GMT
How about a README.md in the repo root and display it on the package's page?
Comment by Johannes Dewender (JonnyJD) - Monday, 24 August 2015, 23:29 GMT
A current use case is because some users of packages like
https://aur.archlinux.org/packages/cower/
simply don't read any previous comments. Not at all.
70 comments and a dozen posted solutions for the same problem since january,
but people still post their "problem" as if they were the first to find out.

Some kind of "pinned" comment or announcement that is displayed above the comment box would help (I hope).
Comment by kozaki (kozaki) - Saturday, 05 September 2015, 13:14 GMT
+1 for the README.md displayed on the package's page. Makes an easy workflow for maintainer, and ease the comments' flow :).
Or for a "pinning" comment system.

Loading...