> > > yep, we are under the process of changing the way we upload new packages:
> > > we would rather upload the SRPM, and a robot shall try to recompile it on
> > > the various (validated) architectures before "enabling" it.
> > Perfect!!!
> > (you guys are making me drool ;-) )
> Okay, actually, we had an internal discussion here. Apparently this would
> cause too much problems.
????
> Actually, what I told was a suggestion of some persons here, but it will
> be too much problematic to be adopted ; also, the guys involved in the
> ports know the kinds of problems that the package usually face, so the
> current process seems more efficient.
So... as I understand it, "problems" will be "stuck" until the
maintainer of
the port goes ahead and figures them out?? I personally like the idea of
the buildrobot handling all the builds. If something goes "wrong" (some
put
a "i386" in a perl package again) then they would be notified about it.
The "problem packages" are more of an exception than the rule.
I myself build on alpha and i686 here, things go reasonable automatic.
The packages that really won't build on alpha are mostly arched out by
now
> Sorry to have transmitted too quick, something which was just under
> discussion.
:-/
Stefan
