GNOME 2.4 make install errors

[Simon Barner]

> > Joe: Perhaps one should add the scrollkeeper example to FAQ #2?
> 
> I don't think it would do any good.  Most people completely miss the
> real error altogether, and simply paste the [useless] tail end of the
> make install.  That's why I think an output interpreter (adamw suggested
> one a while ago) would be a big win.  It could recognize things like
> this, and either prompt users for more input, or direct them to a
> solution.

Wow, nice idea! This inspired me to a different approach, closer to the
root of the error.

Whenever the major version bump of a dynamic library is increased, the
user gets a hint to run `portupgrade -r library'.

I am sure that a lot of users do not use portupgrade as intensively as
they are supposed to, probably because of compilation time, bandwith or
the policy not to update any ports without need which is found quite
often in a production environment.

But if a warning was presented to users that the update of a port had
introduced runtime issues for a list of other ports (perhaps this list
could be included in that warning), they would more likely be motivated
to use portupgrade in order to prevent from those upcoming problems.

OTOH, shouldn't those problems be avoided by the library compatibility
cache in ${LOCALBASE}/compat?

Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: Digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20031124/8fe936b5/attachment.bin