not everyone supports virtual/cdrtools so dropping the USE=cdr isnt so good ...
The problem I tried to fix is too many people not having enough sense to USE=cdr and then trying to build a freakin' LiveCD. At this point, I'd rather do the (ugly) !arch checks than revert the change. Which architectures are we referring to, specifically?
well, `repoman` was used when committing, you'd see s390 doesnt have that package KEYWORDed at all ... but really it affects arches that dont have bootable cd media like arm/m68k/mips/sh/s390/s390x
OK. Let's take this another way, then. Exactly which architectures have no versions of anything providing virtual/cdrtools available. Remember, we're talking about using things like "mkisofs" which is what we're requiring virtual/cdrtools for in the first place. Of your list, at least MIPS doesn't belong on it, since we've hacked up catalyst to build proper MIPS bootable media for the few machines that have optical drives. Even s390 has app-cdr/cdrtools versions marked stable, which is why I am asking for clarification. I'm using virtual/cdrtools. It seems that on s390, at least, the virtual is broken, since it has no version of app-cdr/cdrkit stable, as you said. I think what needs to be fixed is the virtual needs to be updated for s390.
Before: RDEPEND.bad 1 dev-util/catalyst/catalyst-2.0.3.ebuild: ~s390(default-linux/s390/2006.0) ['app-cdr/cdrkit'] After: RepoMan scours the neighborhood... digest.assumed 2 digest-catalyst-2.0.2::catalyst-2.0.2.tar.bz2 digest-catalyst-1.1.10.10::catalyst-1.1.10.10.tar.bz2 RepoMan sez: "You're only giving me a partial QA payment? I'll take it this time, but I'm not happy." What did I change? I added "virtual/cdrtools app-cdr/cdrtools" to default-linux/s390/virtuals and that did it.
This was actually FIXED a long time ago, I just never closed the bug.
