Dirk Schönberger wrote:
I just shortly looked at it and I don't know all intricacies, but I see
the use of {PV}.
I real frameworks, a new version of the headers or libraries is assumed to
be installed if "major changes", i.e. source incompatible API changes,
occur. IIRC, {PV} changes with each new minor version or -r version? So
this may possibly create too many versions. Does there exist a variable
which changes less often, or should there be introduced such a variable?
I'd read this about major version changes... AFAIK there is no way to
test for external API changes via a variable name. The best we can do
is read the upstream changelog. The other thing to note is that unless
the library is slotted, portage will uninstall the old version of the
library (default behavior, iirc) leaving only the most recent version in
the framework.
I'm open to suggestions.
Also, are there any libraries in particular with which you'd like to see
this working? What packages should I be using to test this?
-Nick
--
[email protected] mailing list
