Re: [Condor-devel] Official Debian package for Condor

[Michael Hanke <michael.hanke@xxxxxxxxx>]

On Tue, Dec 07, 2010 at 03:42:54PM -0500, Michael Hanke wrote:
> I'm compiling a list of questions regarding the packaging -- most of
> them concerning a proper port to Debian's glibc.

I'd be glad if I could get some pointers to GLIBC-related issues. The
upcoming Debian release will come with GLIBC 2.11. Condor has not been
ported to this version yet. If I look into the code I find long chains
of 'defined(GLIBC21) || defined(GLIBC25 || ...'. What is the desired
strategy to port Condor to a newer GLIBC version? It looks like I can
only inspect every ifdef and append to the chain. I wonder whether there
is a better approach? Let's say the behavior of GLIBC 2.11 and 2.7 is
identical, I'd still have to add GLIBC211 explicitely.

Is it possible to, by default, treat newer GLIBC versions like the
latest GLIBC version that Condor has already been ported to (and only
handle actual differences between these two versions)?

Related to that: What is the reason to categorically disable the
standard universe build whenever the GLIBC version is unknown? Are there
actual problems, or is it simply to limit possible build environment to
trusted grounds?

Thanks,

Michael

-- 
Michael Hanke
http://mih.voxindeserto.de