Am 2007-03-09 13:52, Dennis Gilmore schrieb:
Once upon a time Friday 09 March 2007, Oliver Falk wrote:
Am 2007-03-08 17:40, Dennis Gilmore schrieb:
On Thursday 08 March 2007 10:34:59 am Oliver Falk wrote:
Am 2007-03-05 20:52, Oliver Falk schrieb:
Sergey Tikhonov schrieb:
We Are planing on adding secondary Archs right now sparc and ia64 are
planned
OK. Fine. At least there are plans for sec arches...
alpha if there is a team to support the arch.
Voting myself for supporting it. However, I will - of course - not be
able to do this alone. Anyone else standing up? I have a few names in my
mind, but don't want to 'speak' 'em out, since those persons must have
enough spare time for doin' the job and of course must be willing to do
so...
> that want to work with fedora.
Secondary arches will get things built automatically when built for a
primary arch.
ack.
> Don't forget there is no longer a core/extras distinction. only
fedora.
For course, I know.
Aurora currently has core and extras for SPARC. the idea is already out
there. the second phase of koji will be adding secondary archs.
OK. So koji will support it sooner or later. I don't know how Aurora
does it. Are they in some way connected to the Fedora CVS/the buildsystem?
Right now for aurora im using plague and some scripts that rsync the srpms and
queue them to build. Any bugs that need fixing we submit patches and make
sure they work for other archs also.
OK. I see.
And another thing. Will package maintainers be aware of the second
arches? Do they also receive notification 'bout failed builds on alpha,
ia64, sparc? If they don't want to fix bugs on the secondary arches,
they should exclude the arch, so the secondary arch builders don't get
overloaded with packages that will not build...
Secondary arch teams will get failure notifications. If a build fails on a
primary arch it must fail on secondary archs. if a build fails on a
secondary arch then it will not affect the primary arch.
Sure. But what if it works fine on primary arch(s) and doesn't on
secondary arch? If the pkg maintainer isn't aware of this problem, he
will never exclude this arch and will - every time he requests a build -
enqueue a package that will not work on the secondary arch... Or will
the secondary arch teams be allowed to exclude packages that do not
build? This means, that secondary arch teams must be (cvs commit)
allowed to every project...
in the new package db we could perhaps add the ability to have maintainers be
included/excluded from secondary archnotifications. based on there own
preferences.
OK. Yes, that sounds fine. Voting for setting this to enabled by default!
-of
