[aur-general] Should we recommend removing comments from the AUR?
AUR Comment for tmux-mem-cpu-load-git from https://aur.archlinux.org//pkgbase/tmux-mem-cpu-load-git/ dlin wrote: Please remove old comment or fixed issues to keep AUR clean. 2014/12/01 2.2.1.r3 remove 'v' in version and depends 2013/08/18 v2.2.1-1 use pacman 4.1 method to pull git source, added pkgver() What is your take on this idea?
This seems like a hack, why not just use a real issue tracker? For example, I use GitHub Issues to track issues related to my AUR packages, and then the AUR comments become something more like a News page for that package. I thought there was a plan for AUR to move to something more VCS-oriented for tracking changes in PKGBUILDs (i.e. AUR git hosting), and that might come with issue-tracker-like capabilities, but I'm not sure what the state of that is currently or who is working on it. Maybe TUs/devs can chime in as that may solve this use case for comments on its own? (NB: If the intention would be to make maintainers able to remove comments, then there are many packages without maintainers where people "adopt, update, orphan" when there's an update - it'd be important to protect those packages against automated mass-comment-removals by malicious third party.) On Mon, Dec 1, 2014 at 12:15 PM, Karol Blazewicz <karol.blazewicz@gmail.com> wrote:
AUR Comment for tmux-mem-cpu-load-git from https://aur.archlinux.org//pkgbase/tmux-mem-cpu-load-git/ dlin wrote:
Please remove old comment or fixed issues to keep AUR clean.
2014/12/01 2.2.1.r3 remove 'v' in version and depends 2013/08/18 v2.2.1-1 use pacman 4.1 method to pull git source, added pkgver()
What is your take on this idea?
Sorry for top posting accidentally.
On Monday, December 01, 2014 18:15:22 Karol Blazewicz wrote:
What is your take on this idea?
I personally don't like the idea of removing comments. I think a real issue tracker would be ideal, but also a decent substitute would be to be able to mark comments as an issue/bug when they are posted, and having the maintainer be able to mark them as resolved, although that may actually be more difficult to implement. I would like to note that I'm also perfectly happy with the current situation, but if something were to be done the above is what I'd like to see instead of comment deletion. -RDM
I prefer bug tracking too. But that will require extra people to handle dangling bugs. I don't like the removing comments method. But, That's just a workaround. I also use the comment to keep a simple history for others who want to know. These methods are learned from other AUR packages. (I forgot whom). On Tue, Dec 2, 2014 at 8:15 AM, Robert Mackanics <schnoopay@gmx.com> wrote:
On Monday, December 01, 2014 18:15:22 Karol Blazewicz wrote:
What is your take on this idea?
I personally don't like the idea of removing comments. I think a real issue tracker would be ideal, but also a decent substitute would be to be able to mark comments as an issue/bug when they are posted, and having the maintainer be able to mark them as resolved, although that may actually be more difficult to implement.
I would like to note that I'm also perfectly happy with the current situation, but if something were to be done the above is what I'd like to see instead of comment deletion.
-RDM
I agree with bug tracking. I only have one problem with it: I already use a bug-tracker on GitHub for software that I've written myself, but people always report bugs in the comments regardless. It'll be a paradigm shift which is going to take time, and there'll be a long transition period we'll have to put up with. -- David Phillips GPG Key 0x7BF3D17D0884BF5B Fingerprint 2426 235A 7831 AA2F 56AF 4BC0 7BF3 D17D 0884 BF5B
I agree with bug tracking. I only have one problem with it: I already use a bug-tracker on GitHub for software that I've written myself, but people always report bugs in the comments regardless. It'll be a paradigm shift which is going to take time, and there'll be a long transition period we'll have to put up with.
A custom field in PKGBUILD that AUR will understand would really come in handy. Something like this: pkgissues='https://github.com/Nowaker/aur-packages/issues' <p> <input type="submit" value="Add Comment"> If you can't build the package, or the package is broken, please <a href="https://github.com/Nowaker/aur-packages/issues">report an issue</a> instead. </p> -- Damian Nowak www.virtkick.io
On 02-12-14 07:07, Nowaker wrote:
A custom field in PKGBUILD that AUR will understand would really come in handy. Something like this: pkgissues='https://github.com/Nowaker/aur-packages/issues' <p> <input type="submit" value="Add Comment"> If you can't build the package, or the package is broken, please <a href="https://github.com/Nowaker/aur-packages/issues">report an issue</a> instead. </p>
Not a bad idea, but it would require makepkg to support it. Official repos have "bug reports" / "add a new bug" links on the package page, so they don't need this option. How about a similar field on AUR package page ? it should be empty by default, editable for maintainer
On Tue, 02 Dec 2014 11:43:05 +0100 LoneVVolf <lonewolf@xs4all.nl> wrote:
On 02-12-14 07:07, Nowaker wrote:
A custom field in PKGBUILD that AUR will understand would really come in handy. Something like this: pkgissues='https://github.com/Nowaker/aur-packages/issues' <p> <input type="submit" value="Add Comment"> If you can't build the package, or the package is broken, please <a href="https://github.com/Nowaker/aur-packages/issues">report an issue</a> instead. </p>
Not a bad idea, but it would require makepkg to support it. Official repos have "bug reports" / "add a new bug" links on the package page, so they don't need this option.
How about a similar field on AUR package page ? it should be empty by default, editable for maintainer
I for one would really like to see a field on the AUR where I as buildscript maintainer can enter comments regarding the package, like X is broken right now, for y use workaround z, etc. -- Joakim
On Tue, Dec 2, 2014 at 1:12 PM, Joakim Hernberg <jhernberg@alchemy.lu> wrote:
On Tue, 02 Dec 2014 11:43:05 +0100 LoneVVolf <lonewolf@xs4all.nl> wrote:
On 02-12-14 07:07, Nowaker wrote:
A custom field in PKGBUILD that AUR will understand would really come in handy. Something like this: pkgissues='https://github.com/Nowaker/aur-packages/issues' <p> <input type="submit" value="Add Comment"> If you can't build the package, or the package is broken, please <a href="https://github.com/Nowaker/aur-packages/issues">report an issue</a> instead. </p>
Not a bad idea, but it would require makepkg to support it. Official repos have "bug reports" / "add a new bug" links on the package page, so they don't need this option.
How about a similar field on AUR package page ? it should be empty by default, editable for maintainer
I for one would really like to see a field on the AUR where I as buildscript maintainer can enter comments regarding the package, like X is broken right now, for y use workaround z, etc.
--
Joakim
You can start a thread on the forums.
Comments have a timestamp. You can, after all, just compare the comment date with the package's upload date. And then again. We could actually have comments more recent than the last source package upload have a wee bit stronger contrast and maybe *bold* font. cheers! mar77i
I think that a bug tracker would be the best solution, and i see removing comments just as a temporary, hacky solution. as comments are just used for bug tracking anyway. (so we can just replace the comments block below the AUR package with the bug tracker) But if we change it, it should be build like github to be tightly integrated with an underlying VCS to which the AUR package publisher and the AUR trusted users have commit rights.
On Tue, 02 Dec 2014 15:11:01 +0100 mrlemux <mrlemux@gmail.com> wrote:
comments are just used for bug tracking anyway
No, they provide useful information, at least for those of us who are using the frowned upon yaourt. If I run 'yaourt -S' I like to see the comments, because then I don't need to check a bugtracker or even the AUR website first, to see if a PKGBUILD might be broken and what workarounds already were done by others.
On 2014-12-02 13:40, Martti Kühne wrote:
Comments have a timestamp. You can, after all, just compare the comment date with the package's upload date. And then again. We could actually have comments more recent than the last source package upload have a wee bit stronger contrast and maybe *bold* font.
cheers! mar77i
I'd love to see markdown support on the AUR. It's simple enough, but makes a huge difference. Especially when you bundle plenty of links, lists, etc. Also, since markdown is so simple, it can be emailed as-is in plain text. -- Hugo Osvaldo Barrera A: Because we read from top to bottom, left to right. Q: Why should I start my reply below the quoted text?
On Tue, Dec 2, 2014 at 6:12 AM, Joakim Hernberg <jhernberg@alchemy.lu> wrote:
I for one would really like to see a field on the AUR where I as buildscript maintainer can enter comments regarding the package, like X is broken right now, for y use workaround z, etc.
...along with this, the AUR pages should parse 'changelog=' and display the changelog as provided by the packager. The feature is already there, all we need is the website to parse & display. $0.02, -te
participants (13)
-
Daniel YC Lin
-
David Phillips
-
Hugo Osvaldo Barrera
-
Ido Rosen
-
Joakim Hernberg
-
Karol Blazewicz
-
LoneVVolf
-
Martti Kühne
-
mrlemux
-
Nowaker
-
Ralf Mardorf
-
Robert Mackanics
-
Troy Engel