| 1 |
On 09/14/2016 09:21 AM, Alexis Ballier wrote: |
| 2 |
> |
| 3 |
> Guess you never had to maintain packages whose releases are only |
| 4 |
> snapshots. They're trivial but it's a waste of time to re-assemble all |
| 5 |
> the bits every couple of months when you want to make a snapshot. |
| 6 |
> |
| 7 |
> Questions one needs to answer: |
| 8 |
> |
| 9 |
> - What SCM is used ? |
| 10 |
> - What is the URI ? |
| 11 |
> - How to fetch it ? |
| 12 |
> - What should be cleaned up after fetching ? |
| 13 |
|
| 14 |
These are all the same question, which does take a second to google, but |
| 15 |
isn't all that time consuming. |
| 16 |
|
| 17 |
|
| 18 |
> - What dirname to use so that it matches ebuilds' $S ? |
| 19 |
> - What compression to use so that it matches SRC_URI ? |
| 20 |
|
| 21 |
cat Manifest |
| 22 |
|
| 23 |
But seriously, once you've googled the repo, you might notice that it's |
| 24 |
hosted at github, and that you don't need to create your own snapshot |
| 25 |
tarballs any more. Want a snapshot from 20150423? Try, |
| 26 |
|
| 27 |
https://github.com/pathscale/libcxxrt/archive/665b0223ee27547175dc327a386fcd88243c7677.tar.gz |
| 28 |
|
| 29 |
Put COMMIT=665b0223ee27547175dc327a386fcd88243c7677 in the ebuild, stick |
| 30 |
that in $SRC_URI and $S, and then future snapshots will work without |
| 31 |
modification. |
Archives