On 11/11/2016 01:19 PM, Julien JPK wrote:
> I have a few things to review before I start working on actually
> significant package updates. I'll make sure I have a cleaner "AUR
> maintaining" environment to avoid missing such obvious errors in the
> future. I'll also make myself more acquainted wit
On 11/11/16 17:47, Giancarlo Razzolini via aur-general wrote:
> Using a helper to confirm if a PKGBUILD is "ok" is so bad of a practice
> that I don't even know where to begin. Use the tools for the job, makepkg
> and, devtools. Let the helpers to deal with it. It's their job to make
> sure your pa
On 11/11/2016 12:14 PM, Julien JPK wrote:
> To be honest I was just picking packages I was interested in, with the
> idea of maintaining them on a longer term should it become necessary. I
> understand that the packages I've chosen so far are not tremendously
> active, I just thought these simple u
Em novembro 11, 2016 15:14 Julien JPK escreveu:
On 11/11/16 16:45, Doug Newgard wrote:
Alright so now I'm really lost. I'm certain I built and installed the
package successfully before sending the new PKGBUILD, and now that I try
again, I do get the errors. I must have forgotten something when I
On 11/11/16 16:45, Doug Newgard wrote:
> The checks are done by pacman. I'm guessing you haven't tried with makepkg +
> pacman -U since the boost update.
Alright so now I'm really lost. I'm certain I built and installed the
package successfully before sending the new PKGBUILD, and now that I try
a
On 11/11/2016 11:37 AM, Julien JPK wrote:
> Hello!
>
> I recently started maintaining small AUR packages (basically just
> updating version numbers on git packages and so on), and I came into a
> little situation when updating the boost-compute [1] package.
Do you mean, pushing a new pkgver after
On Fri, 11 Nov 2016 16:37:23 +
Julien JPK wrote:
> I'm guessing the reason why the makepkg approach works is because it
> doesn't run these checks, and the boost files are simply overwritten
> (the PKGBUILD runs a simple cp). So here's what I'm hesitating about:
The checks are done by pacman
Hello!
I recently started maintaining small AUR packages (basically just
updating version numbers on git packages and so on), and I came into a
little situation when updating the boost-compute [1] package.
The package is basically a header-only library, typically providing
files under /usr/includ
