> > A tiny correction: NetBSD/i386 1.5 ships with XFree86 3.3.6, not
> > 3.3.3.  Not that that helps you a whole lot.  (^&
> 
> It's actually 3.3.6 + selected pull-ups from 3.3.9.

Ah.  I wasn't aware of that.  Maybe the 1.5 version shouldn't call itself
3360 for the version number, then..?


> > If you upgrade X, you should be prepared to rebuild any/all packages that
> > you've installed from pkgsrc.
> 
> That's not true at all. XFree86 4.0.2 is backwards compatible with 3.3.6.
 [...]

Some (freshly inregrated) stuff winds up in different places, though.  
Doesn't ELFness require that the binary know the directory in which the
library resides?  If so, then there's some stuff that needs to be rebuilt:

 [...]
> How about: "for p in Mesa xfstt xpm; do pkg_info -R $p >>LIST; pkg_delete
> -r $p; done"? Then upgrade X, and rebuild the packages in "LIST".
> Actually, "Mesa" should be rebuilt, too, because it supplies some missing
> pieces from the XFree implementation.

That's probably fine, but you'll end up rebuilding a LOT of stuff anyway
(at least, that's the way it seems to work for me).  There tend to be
cascading dependancies, and pkgsrc isn't smart enough to figure out that
the library version hasn't changed.  E.g., qt depends upon Mesa.  
Anything that uses qt will have to be rebuilt, in order to build Mesa.  
Similarly, lots of thins use XPM, I think.

Trying to seperate them out would be tedious.

And, from first hand experience, I can tell you that if the build process
breaks mid-way for some reason (e.g., a package temporarily broken), you
can have a mess if you don't have a list of ALL packages that were
installed before you began.

It's not always necessary, but it is always prudent, IMHO.


  "I probably don't know what I'm talking about." --rauch@eecs.ukans.edu