[arch-general] Default value of "j" in makeflags of makepkg.conf

David C. Rankin drankinatty at suddenlinkmail.com
Sun Jan 5 20:11:12 EST 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/03/2014 09:26 AM, Thomas Bächler wrote:
> Error and inexperience can occur while learning. If you upload to the
> AUR, I expect you to have polished and finished material, not your first
> draft.
> 
> There's enough places with kind people who will look at your PKGBUILD
> and point out your mistakes. The AUR isn't one of those places.

  What I've noticed is many times "error and inexperience" are not what break
PKGBUILDs in AUR, rather it is rapid change in both the source and in Arch, that
render what was a correct PKGBUILD broken almost overnight. I agree with TB that
what gets uploaded to AUR should be a correct finished product, at the same time
we shouldn't, in hindsight, beat up on packagers when breaks are the result of
either source changes or Arch changes. This is especially true when building
large source projects where Arch is several major versions ahead of what many
contributors use (gcc, etc..).

  The past year has seen incredible changes in Arch, as well as in many
packages, and as a result I've noticed that many packages I need from AUR need
to be updated. Hopefully going forward we won't be changing from systemd to
something else or moving chunks of the filesystem around for a while which
should allow many of these problems to work themselves out :-)

- -- 
David C. Rankin, J.D.,P.E.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLKArAACgkQZMpuZ8CyrciZ7wCfQIjMCXZX3TrtxSpvzqWwS4oZ
UUsAniz+DOthsldJY2Ob93bII/0Xn57W
=Ph03
-----END PGP SIGNATURE-----


More information about the arch-general mailing list