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 tried
the first time. So basically since that's not an option anymore, I'm
guessing the package is no longer of any use separately.
Packages re-use the building directory. This is were building in a clean
chroot comes in handy. At minimum, use makepkg's -C option.
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 update tasks would be a good place
to start after the wiki. I guess that was yet another mistake...
Nothing wrong on maintaining the occasional package.
I'm not quite sure where you're going with this. While I'm not actually
a yaourt user, I thought it would be a good way to "confirm" that the
update had gone through and the updated package was indeed available.
Now I'm guessing my 3rd mistake is hidden somewhere in there.
Thank you for your answers, and sorry for the disturbance. Turns out I
just hadn't been thorough enough in my work.
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 package installs (provided you follow best practices).
Cheers,
Giancarlo Razzolini
