Re: reimport mesa 18, remove old MesaLib packages

[Greg Troxel <gdt%lexort.com@localhost>]

I generally do not like renaming because it breaks automatic upgrades,
but if that is broken anyway (because most people are running 18??),
then moving to a name that is better aligned with upstream and in use in
other packaging systems (?) sounds good.

Do you literally mean 'mesa', or do you mean 'mesa18'?  It seems that
the history of mesa is messy enough that it has earned a long-time stay
in the status of only being versioned.  Or do you think that you can not
only remove all the other versions, but that we will be able to have
exactly one version at all times over the next 3 years (meaning
just upgrades, but not needing to have an older one for anybody for any
reason)?