[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: introducing brockenboring
From:       Daniel Stone <dstone () kde ! org>
Date:       2003-06-25 22:00:20
[Download RAW message or body]


On Wed, Jun 25, 2003 at 05:19:32PM +0200, Stephan Kulow wrote:
> Currently our kdeinit support in the Makefiles lack
> as the kdeinit modules are installed in parallel to
> a binary linking against these modules. This has
> some drawbacks:
> 
> 1. glibc's ldconfig doesn't cache DSOs that don't 
>   match the lib*.so* pattern, so starting konqueror
>   won't be able to use the cache to find konqueror.so
> 2. (more important) this doesn't work at all on non-ELF
>   systems (have you asked who the hell is using non-ELF
>   these days? Mac OS X does)
> 
> Benjamin Reed once tried to get am_edit to create a
> shared library per KLM and then link both the KLM and 
> the binary to it. As he failed, he tried the same for unsermake.
> Problem with unsermake is: automake users will fall behind
> without kdeinit support at all.
> 
> So we made a short brain storm session today and came up
> with the following idea: install a kdeinit module only and create
> in bin a link to a binary that will be kdeinit without kdeinit:
> "one binary to rule them all".
> 
> So here is the patch to do exactly that: introducing brockenboring

a) whoohoo! This sounds like an excellent idea, and reinforces the fact
   that your toolchain knowledge scares the crap out of me.
b) What does 'brockenboring' mean in English?

-- 
Daniel Stone 	     <daniel@raging.dropbear.id.au>             <dstone@kde.org>
KDE: Konquering a desktop near you - http://www.kde.org

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]