Bryan Østergaard wrote:
A. ~arch keywords are supposed to be carried over to new versions unless
we're talking about big rewrites or similar (so old versions doesn't
have to linger around in portage tree at all).
right, we all agree :)
B. If we're complaining about MIPS team not being able to ~mips kde-meta
on time we need to remove all the arch teams that falls behind from
time. I think that leaves us with maybe x86, amd64, sparc as *the only*
arch teams allowed to keyword kde-meta which is completely insane and an
insult to our users.
every arch team is allowed to keyword kde-meta, just they should not
complain about their keywords not being on bumps when they are late.
Keyword<->ebuild separation allows to clearly show the arch teams that
they are responsible and allows the developers not to get into conflict
here. It clearly would have avoided the recent conflict.
The problem is with ebuild developers like me having no means to get
arch teams to keyword stuff yet we are responsible if something fails
and we get bugs assigned.
[remove kde-meta talk]
Besides that splitting keywords out from ebuilds doesn't solve
*anything* at all related to this as the ebuilds *still* have to stay
around as long as they have keywords. Just like current policy says.
Moving metadata to another place doesn't change that at all.
yeah. A script for removing all ebuilds that are allowed to be removed
by policy would be cool. Sadly I don't have one currently :(
We can for example also offer x86-only sync trees without all the
ebuilds that are only relevant to the other arches.
Best regards,
Stefan
--
gentoo-dev@gentoo.org mailing list
