From: Bill F. <bil...@mi...> - 2004-11-02 03:00:40
|
I think the general rule is if the package is generally available in most all distros, then it's OK to just have a dependency for it. If the package has to be downloaded separately from a third party site or if it's been heavily tweaked/optimized for use by xine, then it's generally included with xine itself to make life easier for most casual users. I think gettext would fall under the first case so it should probably be OK to use the external package (and hope the newer version wouldn't introduce/expose too many new bugs). -Bill On Mon, 1 Nov 2004, Alien wrote: > i find it really odd that alot of stuff is included in your project, most of > which is available in seperate packages... > > Op maandag 1 november 2004 17:59, schreef Michael Roitzsch: > > Hi team, > > > > > I've been working on porting xine-lib to Mac OS X, and one problem > > > which I haven't managed to solve yet is that the intl/ directory in the > > > xine-lib CVS tree simply doesn't compile properly on the Mac. I > > > suspect this is because xine uses an intl distribution from a very old > > > gettext tarball, so would it be possible to upgrade to a newer version > > > of gettext at all? I'd commit a new version myself, but I have no > > > experience with gettext, so I don't know how to import a new intl/ > > > tree, and I wasn't sure if there would be any compatibility problems in > > > doing so. > > > > This old intl directory has bothered me too and I wonder what the common > > solution is. Do all projects that use gettext include a copy of it? > > Couldn't we just require gettext being installed in a recent version? |