I agree that there should be an easier method that doesn't require TU
intervention. However, 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 and I'm pretty sure I read that the
AUR is only getting bug fixes from now on. Well...Unless any user
decides to make the changes and submit a pull request ;-)
-Dustin / lots.0.logs
On Wed 27 Nov 2013 08:28:07 PM CST, Daniel YC Lin wrote:
I think this is a good idea to make AUR PKGBUILD maintainer get multiple
choose when something wrong. And people may branch out without require
TU's permission.
On Thu, Nov 28, 2013 at 8:11 AM, 01walid <[email protected]> wrote:
Greetings,
I'm new to this mailing list. and first of all, sorry if the idea I'm about
to introduce is repeated or annoying (discussed before), I just want to
suggest it.
*What I noticed:*
- Many AUR package maintainers/submitter are developers, or at least
have a VCS knowledge (and a Github, Bitbucket ..etc account)
- Almost all AUR comments are just PKGBUILDs adjustments, suggestions,
enhancement, fixes, new links/md5's or bug reports, written in the
comment
itself.
- Many updated PKGBUILDs do just what suggested in comments (not so
DRY), just a copy and a past (the community is helping).
- Many outdated PKGBUILDs are just outdated because the package owner is
too busy to update it.
*What I suggest:*
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), the link is visible in the package details page. so when
the PKGBUILD is outdated or has a problem, the community can suggest pull
requests directly to the repo, and make the life easier for the package
maintainer.
If you want to go further (and I don't know how's that technically feasible
right now), you can make something that automatically pull the PKGBUILD
directly from the repo link (or the PKGBUILD file direct link from that
repo)
That's it, correct me if I'm just talking nonsense.
Thanks.
--
*Dustin Falgout*
Antergos Dev Team
E-Mail: [email protected] <mailto:[email protected]>
Google/Skype: dustinfalgout
IRC Chat: #antergos
<http://webchat.freenode.net/?channels=antergos&uio=d4>
<http://antergos.com/>
