Here's the URL of the buildoutputs on my sys:
http://d10179.dtk.chello.nl/build/
I've devided it up into contrib, cooker and crypto. Then the arch (I
have
alpha and i586). Then it's into how the packages compiled:
OK/ packages that compile fine.
arch_excl/ packages that have the architecture excluded
broken/ packages that are broken. .spec file that have serious errors,
patches that can't be applied, etc. etc.
dependancies/ packages that need dependancies to be resolved in order
to be compiled. I try to install the dependant packages
ASAP.
fixed_uploaded/ packages for which a fix has been made & made available
here we're waiting for the fix to be integrated into cooker.
interactive/ packages that require human intervention during compiling.
man/ packages with man & info page problems (due to the switch
to spec helper).
obselete/ packages that have become obselete. This is mostly related
to the contribs.
problem/ packages with "problems". They don't compile, or other things
are wrong.
root_only/ packages that can only be compiled as root. Mostly due to dev
entries that need to be made.
If you're interested, please take a look... Be patient with the link,
I've only
got 16Kb/sec upload on my cable connection... AND: these are NOT the
official
cooker builds... Just my personal version of it... I try to compile all
the
packages every week on both of my systems...
Feedback & fixes & sugguestions and sollutions are welcome...
Stefan van der Eijk
Stefan van der Eijk wrote:
>
> OK... it compiles fine on both my intel AND alpha systems... Even by
> compiling it as a non-root user. In my opinion there is nothing wrong
> with procps and discussing this is a waste of resources...
>
> If you are interested in which packages FAIL to compile on my cooker
> systems (I've got an intel and alpha system which are both up 2 date
> with cooker), I'd be happy to share the failed buildoutputs with you
> all...
>
> Stefan
