On Mon, Feb 23, 2009 at 10:51 AM, Adriaan de Groot <groot at kde.org> wrote: > On Monday 23 February 2009 14:49:33 Ben Taylor wrote: >> On Sun, Feb 22, 2009 at 6:15 PM, Adriaan de Groot <groot at kde.org> wrote: >> > On Saturday 21 February 2009 04:05:20 pm Lukas Oboril wrote: >> >> I think we should save our original FOSSgettext, FOSSlibiconv combo to >> >> prevent another build troubles >> > >> > I'm really not very happy with that, simply because of the horrors >> > involved with having three (Sun iconv, GNU iconv, and our own) iconv >> > libraries and three gettext libraries installed on the system. I can live >> > with libcdio being made smart enough to find the SUNW gettext, though. >> >> seeing as I've taken on the S10 builds, I have no issue other than I want >> it to build/work with minimal effort. > > Right. S10 is a different beast from OSOL or Nevada, though: the chances of > getting Sun to ship KDE4 for S10 are, frankly, a lot lower than for the other > two.
I'm aware of that. But since S10 has an already over exposed life span (it should have been gone by 11/07) and there seems to be no end of patching, I figure it a good test bed for the infrastructure, given that what it does have is so old, there is little chance of it's installed tools conflicting. > For nv and OSOL, though, we have to be good citizens (to some extent, at > least). That means that shipping duplicates has to be done with some damn good > reason -- one I don't see on OSOL at the very least. Stefan probably has a better idea of what is going into SXCE these days compared to what's in Dude. I just hope that by depending on Sun's interpretation of "a correct package" install, doesn't make the KDE4 Solaris project lose functionality for nv and OSOL. Like the fact that totem is completely worthless (not that KDE4 uses totem AFAIK, but the fact remains that there is little in Solaris or OSOL WRT audio/video codecs) > On S10, the "minimal effort" route is "build everything" because you are > justified in assuming that everything available on that platform is hopelessly > outdated. So we're not duplicating -- or where we are, "the available version > is 5 years out of date" is a damn good reason enough. By all means, keep > building libcdio on S10 with our own copy of iconv and gettext. yep. > On the other hand, if "minimal effort" means "never looking into reducing our > dependency tree at all" then I'm not buying it. Libcdio looks like it *can* > build with the system iconv, and I'd much rather do that than force a > duplicate out there [[ but I've already said that. ]] And for the most part, I think this is a good idea. *except* that I'm most concerned about anything audio, especially codec related since Sun with Solaris and OpenSolaris has been about as useless as possibly could be. So when we depend on gstreamer from OSOL/SXCE and I look at the list of stuff that S10 builds for gstreamer, and gst-plugin-*, vs what Sun delivers, I tend to be concerned about how feature rich KDE4 on Solaris audio on SXCE and OSOL will be. >> Also, not using FOSSiconv from the perspective on maintaining consistency >> between builds (S10, SXCE, OSOL) is concerning from the prospect of >> problems. (It doesnt' run on S10, it runs on OSOL - type of thing) > > This is true, but we know that S10 and nv are very different beasts; the > latter is supposed to be somewhat up-to-date wrt. Free Software and is a > system where we want to integrate with the rest of the things that are there. yeah, and I keep hearing the demise of SXCE. Though I heard the same for S10... :-) Ben
