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

Am 31.12.2013 07:51, schrieb Sébastien Leblanc: > I would advise against doing that, considering that there are at least a > handful of packages (can't name them) that have broken or otherwise > malfunctioning Makefiles when run in parallel. The package maintainers > _should_ be aware of those issu

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

On Tue, 31 Dec 2013 19:39:03 +0100 Thomas Bächler wrote: > Really? Who? Hmm, me. Intel atom here... > You are suggesting not changing to a sane default because some packages > (especially in the AUR) have crappy maintainers. That's hardly a reason > for anything. A sane default would probably

[arch-general] Patching in PKGBUILDS

Salutations, While debugging a libva-intel-driver issue, I found that makepkg was not reporting failures to patch source files. Is there a reason behind this behavior? Regards, Mark P.S. Happy New Year! -- Mark Lee signature.asc Description: This is a digitally signed message part

Re: [arch-general] Patching in PKGBUILDS

On Wed, Jan 1, 2014 at 4:14 AM, Mark Lee wrote: > Salutations, > > While debugging a libva-intel-driver issue, I found that makepkg was not > reporting failures to patch source files. Is there a reason behind this > behavior? > > Regards, > Mark > > P.S. Happy New Year! > > -- > Mark Lee makepkg

Re: [arch-general] Patching in PKGBUILDS

On Wed, 2014-01-01 at 04:33 +0100, Jan Alexander Steffens wrote: > On Wed, Jan 1, 2014 at 4:14 AM, Mark Lee wrote: > > Salutations, > > > > While debugging a libva-intel-driver issue, I found that makepkg was not > > reporting failures to patch source files. Is there a reason behind this > > behav

Re: [arch-general] arch-general Digest, Vol 110, Issue 18

On Tue, 2013-12-31 at 22:33 -0500, arch-general-requ...@archlinux.org wrote: > On Tue, 31 Dec 2013 19:39:03 +0100 > Thomas B?chler wrote: > > > Really? Who? > > Hmm, me. Intel atom here... > > > You are suggesting not changing to a sane default because some > packages > > (especially in the AUR

Re: [arch-general] Patching in PKGBUILDS

On Wed, Jan 1, 2014 at 4:51 AM, Mark Lee wrote: > My patch command was given in the build() section of the PKGBUILD: > > build() { > cd "${srcdir}/${pkgname}-${pkgver}"; > patch -Np1 -i "${srcdir}/i965_rendering.patch" > ./configure --prefix=/usr > make > } > > While debugging libva-intel-

Re: [arch-general] Patching in PKGBUILDS

On Tue, 2013-12-31 at 23:02 -0500, Mark Lee wrote: > On Wed, 2014-01-01 at 04:58 +0100, Jan Alexander Steffens wrote: > > On Wed, Jan 1, 2014 at 4:51 AM, Mark Lee wrote: > > > My patch command was given in the build() section of the PKGBUILD: > > > > > > build() { > > > cd "${srcdir}/${pkgname}-

Re: [arch-general] Patching in PKGBUILDS

On Wed, Jan 1, 2014 at 5:17 AM, Mark Lee wrote: > On Tue, 2013-12-31 at 23:02 -0500, Mark Lee wrote: >> On Wed, 2014-01-01 at 04:58 +0100, Jan Alexander Steffens wrote: >> > On Wed, Jan 1, 2014 at 4:51 AM, Mark Lee wrote: >> > > My patch command was given in the build() section of the PKGBUILD: >

Re: [arch-general] build and test packages automatically

On Wed, 2013-12-25 at 21:12 -0500, arch-general-requ...@archlinux.org wrote: > Am Sonntag, den 22.12.2013, 19:51 +0800 schrieb Guangyu Zhang: > > [?] and to show the status of all packages which is just like > > the buildd in Debian. > > For my small repositor

Re: [arch-general] arch-general Digest, Vol 110, Issue 18

É quase como se as coisas de cada planeta se fortificassem a toa. Cada decisão errada deles costa sangue. Estaremos acostumados. Enviado do meu dispositivo de rastreamento Em 01/01/2014 01:56, "Mark Lee" escreveu: > On Tue, 2013-12-31 at 22:33 -0500, arch-general-requ...@archlinux.org > wrote: >