| 1 |
> Well since that appears to be some way off, is there any way to get the |
| 2 |
> needed functionality (version string inside ebuild) without a double |
| 3 |
> commit? (Did i read that right?) I'm thinking at worst someone might |
| 4 |
> have to add something to repoman, or a hook on the server end. |
| 5 |
|
| 6 |
another layer of indirection could be introduced: a repo_timestamp file |
| 7 |
which is created when portage is taken from CVS/GIT to the rsync |
| 8 |
mirror... |
| 9 |
|
| 10 |
... this approach makes about 1 million assumptions (rsync_exclude..). |
| 11 |
|
| 12 |
Another idea: the revision could be part of the ChangeLog - a |
| 13 |
monotonically increasing number for every change. added by whoever writes |
| 14 |
the ChangeLog message... |
| 15 |
|
| 16 |
...which is a rather big change, but could be scripted through echangelog |
| 17 |
and family... |
| 18 |
|
| 19 |
kind regards |
| 20 |
Thilo |
Archives