From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 2 Jul 2007 02:45:46 +0200 From: Enrico Weigelt To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Announce: standalone libixp Message-ID: <20070702004546.GC10308@nibiru.local> References: <20070630153814.GA17008@nibiru.local> <5d375e920706300947g5313fe83i9b8a2144293091e@mail.gmail.com> <1183332159.10665.3.camel@linux.site> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1183332159.10665.3.camel@linux.site> User-Agent: Mutt/1.4.1i Topicbox-Message-UUID: 8ec36c02-ead2-11e9-9d60-3106f5b1d025 * Roman Shaposhnik wrote: > On Sat, 2007-06-30 at 18:47 +0200, Uriel wrote: > > Most of your changes don't make any sense to me, pkg-config is at best > > stupid, and shared libraries are plain disgraceful. > > I apologize if I already had sent it out, but I'm close to putting > a petition out there to ban the shared libraries. A petition ? Addressed to whom ? > http://blogs.sun.com/rvs/entry/what_does_dynamic_linking_and Starts w/ typical, stupid U$ flaming: $what_I_hate is like communism. Next logic step would be declaring dynamic linking "unamerican". Well, those ideas are really irrelevant to me. To address some of your points: * Broken compiler: I don't know which compiler you're talkig about. Never ever seen such trouble in recent 15 years. An clean namespace separation would have done the trick. * Bug vs. feature: with clean development methods, it's really clear what some module should do. First design, then implement and test. If you just hack up something w/o any clear spec, you can easily run into trouble. In that case: your fault. * Control over shared code: I *have* control over *all* code on my systems. If necessary, I'm able to lay hands on every module. Actually this is only rarely necessary. I'm not dependent on some "vendor". * Commercial or half-Commercial stuff like OO: I'm neither resposible for their unability to produce clean code, nor do I care. If I, for some reason get interested in such an package, ie. Mozilla, I just break off my own branch and cleanup things as I feel its right. This includes kicking off all these bundled 3rd-party libs. Okay, this was alread too much useless traffic on that issue. If you don't like my branch, simply don't use it. But please stop trying to evangelize me, I'll redirect those efforts to /dev/null immediately. We all have our different destinies and different ways of thinking or coding. IMHO it's best if we try to learn from each other with leaving others in peace, instead of wasting resoures by stupid conflicts. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------