On 06/17/2014 08:49, Rich Freeman wrote: > > Is there a list/etc for crossdev? I'd think that the users and > maintainers of crossdev collectively have the biggest vested interest > in addressing these issues. They're also the ones who can vouch for > how big of a problem this is.
toolchain is the primary maintainer for crossdev. I actually wrote the original implementation of crossdev years ago (~2004?). It was a crappy, overly-complex bash script that didn't use anything portage related (that I can remember) to install a cross-toolchain. It worked for simple toolchains on common arches, i.e., i686 -> mips64 for me to build kernels for the SGI systems. Mike rewrote it several years later to become the crossdev we know and love today, integrating it with emerge and taking better advantage of existing Gentoo capabilities. > Is this having some kind of adverse impact on anybody outside of the > crossdev community? If the crossdev maintainers were pushing hundreds > of packages to change to accommodate dubious design on their part I > could see this being a distro-wide issue. On the other hand, if this > is an issue that only impacts crossdev users and maintainers, then I'd > think the simplest solution would be let them sort it out. I certainly haven't seen crossdev related issues on my systems. Granted, I tend to run rather simple setups, not doing things like i686-on-x86_64 or even running X11. From the earlier-quoted bug, it looked like some X11 package is one of several affected by the issue being highlighted here. What I'd like to see is a list of all affected packages so we all can get a sense of just how big the actual problem really is. All I am hearing so far are unsubstantiated claims of tree-wide breakage. Knowing which packages are broken allows other devs to look at things and maybe come to agreement that crossdev is the source of the problem or perhaps another solution that applies to all of them can be worked up. > If somebody in the crossdev community does want to sort it out and the > problem is package squatting, then that might be a valid reason to > escalate. In that case the cleanest solution is to have a crossdev > project, have the interested devs step up, hold a vote for the lead, > and then respect the lead's role in resolving the issue. Nobody > "owns" a package, but in general we should be careful about stepping > in and overriding maintainers, especially if nobody is interested in > stepping in to take the reins long-term. I'm a member of toolchain, but that's mostly historical because I used to play with a lot of the cross-compile stuff for MIPS and Sparc. Mike and Ryan are the two primaries in toolchain right now. If they don't see a problem with crossdev right now, then I do have to question just how big of a problem this really is. -- Joshua Kinard Gentoo/MIPS ku...@gentoo.org 4096R/D25D95E3 2011-03-28 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic
