You are not logged in.

#1 2006-04-07 00:52:10

syamajala
Member
From: here, there, everywhere
Registered: 2005-01-25
Posts: 617
Website

my new mission!

I am now making it my mission to improve the quality of the PKGBUILDs that make up current and extra. It is not rare for one to find a PKGBUILD that is missing things like md5sums, files listed in the source array, and broken links. From now on when I find such things in PKGBUILDs when building things for arch64 I will report them in flyspray. Hopefully this will have a positive effect and not become an annoyance to the devs.

Offline

#2 2006-04-07 05:03:21

soloport
Member
Registered: 2005-03-01
Posts: 442

Re: my new mission!

Very worthy cause.  Thanks!

Offline

#3 2006-04-07 05:18:34

AndyRTR
Developer
From: Magdeburg/Germany
Registered: 2005-10-07
Posts: 1,641

Re: my new mission!

I often have to look for new working URLs. I will add them to flyspray.

One question: Do all the devs built with MAKEFLAGS="-j1" :?: So often I find packages that won't compile with any number larger than 1. So I often need to add "make -j1 || return 1" or even export MAKEFLAGS="-j1".

Is it wanted to also report this issues or will all packages everytime be build with a strict -j1 makeflag?

AndyRTR

Offline

#4 2006-04-07 13:46:16

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: my new mission!

AndyRTR wrote:

One question: Do all the devs built with MAKEFLAGS="-j1" :?: So often I find packages that won't compile with any number larger than 1. So I often need to add "make -j1 || return 1" or even export MAKEFLAGS="-j1".

Is it wanted to also report this issues or will all packages everytime be build with a strict -j1 makeflag?

AndyRTR

I experienced that with a custom samba rebuild for a X-less server machine. IMO these are upstream bugs and should be reported somewhere. I'm afraid I don't know much about Makefiles, so I cannot say how these compile issues can be fixed.

Offline

Board footer

Powered by FluxBB