Re: [aur-dev] Add a VCS field in the package details page
01walid <01walid at gmail.com> wrote:
Just an *optional* field to be added when submitting the package, where -if available- the package submitter can add the PKGBUILD repo link (on Github, bitbucket ..etc)
Dustin Falgout <dustin at falgout.us> wrote:
I'm not sure that github is the right solution as we would be relying on an outside service that could possibly change or disappear at any time in the future. Perhaps something similar to how wikis allow revisions to be made and viewed by anyone but don't replace the original content until approved?
I don't see a way to do anything about this issue that wouldn't be considered a new feature to the AUR
I think this proposal is something simpler, almost akin to url= in a PKGBUILD. I too keep my PKGBUILDs in a git repo, and sometimes I've even put the github link as the upstream URL. It would be nice if there was a more correct place for that. Maintainers can use their own host, doesn't have to be github. Obviously we're responsible for avoiding dead links, just as in url= and source= etc.
Good point. I guess the real question is should this be handled by makepkg or the AUR website? I don't see it being very difficult to have it done by the AUR website. Of course, the url would have to be placed alone in a separate file (AUR does not and will not parse PKGBUILDS) Perhaps someone that is more familiar with AUR/makepkg development will chime in on this... Best, Dustin On Sat 30 Nov 2013 11:18:57 AM CST, Yardena Cohen wrote:
I think this proposal is something simpler, almost akin to url= in a PKGBUILD. I too keep my PKGBUILDs in a git repo, and sometimes I've even put the github link as the upstream URL. It would be nice if there was a more correct place for that.
Maintainers can use their own host, doesn't have to be github. Obviously we're responsible for avoiding dead links, just as in url= and source= etc.
--
participants (2)
-
Dustin Falgout
-
Yardena Cohen