On Sun, 16 Jan 2005 17:55:40 -0500, Stephen P. Becker <[EMAIL PROTECTED]> wrote: > Well, after discussion among the other mips folks, we are of the opinion > that if the monolithic kde ebuilds are removed, then we just won't > maintain kde on our arch anymore. You just can't expect some of these > non-x86 arches that have smaller dev teams to have the time to mess with > 400+ ebuilds for kde. Also, emerging 400+ ebuilds on many of the > machines we support is just not feasable. Not only that, but the bloat > this brings to the portage tree is awful. I just hope this doesn't go > further in the future to where the ebuilds get spread across the tree > into separate categories. > > Steve
Well, you can expect the arch teams to run an emerge kde-meta for the masked ebuilds and atleast report bugs, no? Also, correct me if I'm wrong, but you apply the patches when you extract the source. If exactly the same source package is extracted and same patches are applied, where would the problem be? -- In all other cases, it will only be a matter of saying, here, we made this patch for the kdebase source (which doesnt make a difference if its on portage on not), and it will be the job of the KDE team to add it to the split ebuilds which I'm sure they'll happily do. Am I completely off here? -- [email protected] mailing list
