| 1 |
> |
| 2 |
> OK. This is my first stab at an ebuild for creating frameworks. This |
| 3 |
> is my first eclass, so please (kindly) point out my ignorance in the |
| 4 |
> matter. It is still very untested; help me get this thing going before |
| 5 |
> I submit it to gentoo-dev. |
| 6 |
> |
| 7 |
> The code is in my darcs-managed overlay: |
| 8 |
> http://code.sbbod.net/portage-overlay/eclass/BPFramework.eclass |
| 9 |
> -- |
| 10 |
|
| 11 |
I just shortly looked at it and I don't know all intricacies, but I see |
| 12 |
the use of {PV}. |
| 13 |
I real frameworks, a new version of the headers or libraries is assumed to |
| 14 |
be installed if "major changes", i.e. source incompatible API changes, |
| 15 |
occur. IIRC, {PV} changes with each new minor version or -r version? So |
| 16 |
this may possibly create too many versions. Does there exist a variable |
| 17 |
which changes less often, or should there be introduced such a variable? |
| 18 |
|
| 19 |
Regards |
| 20 |
Dirk |
| 21 |
-- |
| 22 |
gentoo-osx@g.o mailing list |
Archives