| 1 |
>>>>> On Wed, 2 Dec 2015, Alexis Ballier wrote: |
| 2 |
|
| 3 |
> What's the point, need or advantage in moving this to all-ebuild-scope? |
| 4 |
|
| 5 |
> Usually eclass refactor/api cleanup are done in a -r{n+1} while |
| 6 |
> deprecating -rn. This would have the advantage that you can quickly |
| 7 |
> post a complete implementation and get wider reviews. |
| 8 |
|
| 9 |
A proof-of-concept implementation for the two version manipulation |
| 10 |
functions is here: |
| 11 |
https://482170.bugs.gentoo.org/attachment.cgi?id=418072 |
| 12 |
Add some comments and you'll have a working eclass. :) |
| 13 |
|
| 14 |
Some details are still to be discussed, e.g. what should be the |
| 15 |
behaviour if the version string starts or ends with a separator? |
| 16 |
|
| 17 |
Also version_test is missing, but the idea there was to avoid |
| 18 |
redundancy and use the implementation that already exists in the |
| 19 |
package manager (which does version comparison all the time). This is |
| 20 |
one of the reasons for moving it to the package manager. |
| 21 |
|
| 22 |
Ulrich |
Archives