| 1 |
Dirk Schönberger wrote: |
| 2 |
> I just shortly looked at it and I don't know all intricacies, but I see |
| 3 |
> the use of {PV}. |
| 4 |
> I real frameworks, a new version of the headers or libraries is assumed to |
| 5 |
> be installed if "major changes", i.e. source incompatible API changes, |
| 6 |
> occur. IIRC, {PV} changes with each new minor version or -r version? So |
| 7 |
> this may possibly create too many versions. Does there exist a variable |
| 8 |
> which changes less often, or should there be introduced such a variable? |
| 9 |
|
| 10 |
I'd read this about major version changes... AFAIK there is no way to |
| 11 |
test for external API changes via a variable name. The best we can do |
| 12 |
is read the upstream changelog. The other thing to note is that unless |
| 13 |
the library is slotted, portage will uninstall the old version of the |
| 14 |
library (default behavior, iirc) leaving only the most recent version in |
| 15 |
the framework. |
| 16 |
|
| 17 |
I'm open to suggestions. |
| 18 |
|
| 19 |
Also, are there any libraries in particular with which you'd like to see |
| 20 |
this working? What packages should I be using to test this? |
| 21 |
|
| 22 |
-Nick |
| 23 |
-- |
| 24 |
gentoo-osx@g.o mailing list |
Archives