On Sat, 23 May 2015 11:34:38 +0200
Manuel Reimer manuel.rei...@gmx.de wrote:
Hello,
I'm doing my first steps with AUR 4.0 and I'm asked to commit both,
PKGBUILD and .SRCINFO.
.SRCINFO is automatically created with makepkg --source, but there
is no need for a tarball when pushing to GIT.
* Jonathan Arnold jdarn...@buddydog.org (Wed, 27 May 2015 07:56:20
-0400):
I'd be happy if there was at least a reasonable description
of .SCRINFO on the wiki. There's a glossy version here:
https://wiki.archlinux.org/index.php/Arch_User_Repository#AUR_metadata
But there should be more,
On Wed, 27 May 2015 16:25:13 +0200
Marcel Korpel marcel.kor...@gmail.com wrote:
* Jonathan Arnold jdarn...@buddydog.org (Wed, 27 May 2015 07:56:20
-0400):
I'd be happy if there was at least a reasonable description
of .SCRINFO on the wiki. There's a glossy version here:
* Jonathan Arnold jdarn...@buddydog.org (Wed, 27 May 2015 15:18:43
-0400):
Well, for one, there's no mention on the wiki on how to generate this
file. For another, it seems pretty easy to generate by hand, as the
description indicates (nowhere does it say it gets generated).
Just use mksrcinfo
Generating such a file manually is error-prone, using mksrcinfo ensures
that the file is exactly what AURweb needs.
I believe that is what he is saying should be in the wiki. And since there
are so many questions around it this past week on the mailing list, it
might be a good idea to have it
On Sat, 23 May 2015 at 11:34:38, Manuel Reimer wrote:
Hello,
I'm doing my first steps with AUR 4.0 and I'm asked to commit both,
PKGBUILD and .SRCINFO.
.SRCINFO is automatically created with makepkg --source, but there is
no need for a tarball when pushing to GIT. So what I think that
Hello,
I'm doing my first steps with AUR 4.0 and I'm asked to commit both,
PKGBUILD and .SRCINFO.
.SRCINFO is automatically created with makepkg --source, but there is
no need for a tarball when pushing to GIT. So what I think that would be
useful is something like makepkg --upgradesrcinfo
