From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7403 invoked by alias); 31 Oct 2004 08:52:35 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 7385 invoked from network); 31 Oct 2004 08:52:33 -0000 Received: from unknown (HELO q7.q7.com) (207.173.201.42) by sourceware.org with SMTP; 31 Oct 2004 08:52:33 -0000 Received: from q7.q7.com (localhost [127.0.0.1]) by q7.q7.com (8.12.8/8.12.8) with ESMTP id i9V8qWNf026510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 31 Oct 2004 01:52:33 -0700 Received: from localhost (skeezics@localhost) by q7.q7.com (8.12.8/8.12.8/Submit) with ESMTP id i9V8qWma026504 for ; Sun, 31 Oct 2004 01:52:32 -0700 X-Authentication-Warning: q7.q7.com: skeezics owned process doing -bs Date: Sun, 31 Oct 2004 16:28:00 -0000 From: Skeezics Boondoggle To: xconq7@sources.redhat.com Subject: Re: SDL Interface Development In-Reply-To: <41841290.3040905@phy.cmich.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004/txt/msg01373.txt.bz2 On Sat, 30 Oct 2004, Eric McDonald wrote: [snip] > A while back ago, we considered SDL_Pango for handling of > international and exotic text. Pango (which SDL_Pango obviously > requires) is not without dependencies either. So I think point (2) is > something worth considering. How much should Xconq be able to stand > alone? And how much should we cave in to rapid development at the > expense of raising the hacker "cost of entry", so to speak? [snip] Just to chime in from the Solaris camp - this all sounds great, as long as the dependent libraries are reasonably cross-platform and the build for non-Linux/Windows machines (is that the diplomatic way to say "real Unix" machines? :-) doesn't become untenable. I'd say if it's smaller/easier to bundle those libs with the Xconq sources and build them all in one shot, that's fine, or we'd need to make sure that the configure script can easily find them (or be told where to find them) already installed on the system. Having lived through the years when "all the world's a Vax", then the period of "all the world's a Sun" and now "all the world's the hacked up one-off peculiar Linux box on my desk", I'm just *reeeeeally* tired of constantly screwing around with and patching configure scripts that assume too much. That's my only worry with using third party libs that come with a mile-long dependency list... Also, I've been remiss in building xconq from the latest CVS snapshots for Solaris... I think something was broken the last time I tried it... oh geez, almost a year ago! (November 15th, 2003) I should grab the latest sources and see if the existing stuff still builds on Solaris before griping about possible future changes, eh? :-) -- Chris