The state of UNIX in general and PLD in particular

[Jakub Bogusz]

On Sun, Mar 04, 2007 at 07:30:29PM +0100, Jakub Piotr Cłapa wrote:
> Cezary Krzyzanowski wrote:
> > Dnia 04-03-2007, nie o godzinie 02:46 +0100, Jakub Piotr Cłapa
> > napisał(a):
[...]
> > Moreover there ara apps that use different
> > libs to achieve common goal (like many XML-related libs, many types of
> > threading abstraction, media handling) so naturally one desktop
> > environment would pull *almost* all other deps. Think kaffeine -
> > gstreamer + xine backends. And what - now say 'kaffeine will only use
> > xine' and make similar decisions for other non 'pure' apps?
> 
> If the XML lib is used by only several app that lets bundle it with the 
> apps (very little disk space will be lost this way).
> If the XML lib is used by many GNOME apps than bundle it with the GNOME 
> superpackage.
> If it's used by more than 100 programs from different environments (say 
> DBus) than put it in a general desktop bundle.

Blah, desktop.
Some servers utilize XML as well.

And what about e.g. "apache bundle" and "php bundle"?
php can be used independently. But when it's used as mod_php, it shares
address space with apache. If both use different versions of libraries
in their modules, expect random problems.

> > One thing posted in that paper was translation stuff. There are some
> > aspects of FHS that suck - like putting applications translation files
> > in common dir. It won't be shared anyway. This is stupid - I admit. Then
> > again some translations are reused. How to compromise? Make a
> > loooonnngggg searching paths? Every new applications adds it's paths to
> > translation file paths, binary paths and many, many other? This *will*
> > be unmaintainable in longer run.
> 
> The reused translations are the core GTK ones, aren't they? I don't 
> remember any translations with their own package that is required by 
> other apps.

(g)libc, some other libraries.


-- 
Jakub Bogusz    http://qboosh.pl/