On Friday 03 October 2008 22:35:24 Lukas Oboril wrote: > > My intentions at this point are vague. I'd like to put this stuff up > > somewhere, but I see it as something separate from the work done in Dude. > > It might be good for public perception (for such public as there is) to > > have it in a repo associated with the KDE project on opensolaris.org. > > It's very hard to maintain one repo for S10 and Nevada.
What exactly is hard there? Building package <foo> remains largely the same, doesn't it, whether it is on SXCE or S10? Or are there real and annoying differences in what is detected between the two? Is our current baseline nv version (70b, 83, 91) too old, too wrong, or otherwise broken? Should be push more aggressively for updates to the baseline nv (that would mean I would have to upgrade more than once a year, too). > Nevada is > changing a lot, so we need some more flexible buildsystem for that. In what way would it have to be more flexible? Is building packages too much of a challenge (in which case I'd try to make it easier to re-create the environment the packages use to build stuff) or is the problem in discovering what new breakage is in the new nv releases? I don't chase nv releases, so for me it's a platform as stable and unchanging as any other. > For S10 is our cvsdude is quite enough. [ade]
