Re: Pango-1.13.3 released [unstable]

--- Behdad Esfahbod <besfahbo redhat com> wrote:

> On Tue, 2006-07-11 at 00:06 -0400, Sergei Steshenko wrote:
> > 
> > --- Behdad Esfahbod <besfahbo redhat com> wrote:
> > 
> > 
> > > 
> > >  * Installing this version will overwrite your existing
> > >    copy of Pango-1.12. 
> > 
> > Shameless plug - my tool ( local building and
> > installaion easily allows coexistence of different versions of the same
> > library/application - install (and build) directories are versioned by default.
> This overwriting is quite on purpose, such that external modules written
> for Pango don't have to be reinstalled when a new version of Pango is
> installed.  Your tool is defeating that feature.
> > Regards,
> >   Sergei.
> > 
> > Applications From Scratch:
> -- 
> behdad

Well, suppose there is an application, or its feature which is rarely/never
used by an end user.

Suddenly the user decides to try the feature/application and it doesn't work.

The user recollects that, in this case, new pango has been installed.

So, is the problem with the feature/application because of pango or because
of sometning else ?

My point is that if there is an A application depending on library L, and
library L has a newer version, it's more reasonable to have two installs:

A_newer + L_newer
A_older + L_older

- A_newer and A_older may (and probably should) be the same.

If two installs exist, it's much faster to check whether L_older -> L_newer
transition caused the problem.

For examples, ALSA list is full of "I upgraded to kernel v A.B.C and ALSA
v D.E.F and sound stopped working". And the advice is "Roll back both kernel
and ALSA and find the exact combination which caused the problem".

Well, everybody decides for (him/her)self what the gole is...


Applications From Scratch:

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]