| 1 |
On Wed, 14 Sep 2016 16:41:54 +0200 |
| 2 |
Alexis Ballier <aballier@g.o> wrote: |
| 3 |
|
| 4 |
> |
| 5 |
> So, to sum it up, I have to: |
| 6 |
> - Open a browser, go to github (*) |
| 7 |
> - Find out latest commit hash, copy it |
| 8 |
> - (*) Copy the ebuild, setting a 8 digit version representing the date |
| 9 |
> - Open an editor |
| 10 |
> - Edit COMMIT='...' variable by pasting what was found on github. (*) |
| 11 |
> |
| 12 |
> |
| 13 |
> Thanks, but I prefer by far: |
| 14 |
> - Run a script |
| 15 |
> - Copy ebuild, setting version printed by the script. |
| 16 |
> |
| 17 |
> |
| 18 |
> (*) represents everytime i have to switch my hands between keyboard and |
| 19 |
> mouse |
| 20 |
> |
| 21 |
|
| 22 |
|
| 23 |
You can also abuse `git ls-remote Path/To/Repo` -> list of SHA1s -> ebuild -> sed |
| 24 |
|
| 25 |
But you're back to writing a script =) |
| 26 |
|
| 27 |
Or you can do that manually, it reduces the number of *'s |
Archives