Re: C++ transition stumbling blocks?
> > > Well, AFAICS, ATM there is only one source package named xalan.
> > Strange, I thought there were one for 1.5, 2.1 and 2.2
> Well, I see it makes sense to different source pkg names for *minor*
> releases (enough examples of that out there), but Robert created a new
> source pkg for a *micro* release:
Minor or micro doesn't matter.
Binary compatibility does.
You are mixing up shared library versioning (soversion) and
upstream release versioning.