| 1 |
On Wed, 14 Sep 2016 09:38:45 -0400 |
| 2 |
Michael Orlitzky <mjo@g.o> wrote: |
| 3 |
|
| 4 |
> On 09/14/2016 09:21 AM, Alexis Ballier wrote: |
| 5 |
> > |
| 6 |
> > Guess you never had to maintain packages whose releases are only |
| 7 |
> > snapshots. They're trivial but it's a waste of time to re-assemble |
| 8 |
> > all the bits every couple of months when you want to make a |
| 9 |
> > snapshot. |
| 10 |
> > |
| 11 |
> > Questions one needs to answer: |
| 12 |
> > |
| 13 |
> > - What SCM is used ? |
| 14 |
> > - What is the URI ? |
| 15 |
> > - How to fetch it ? |
| 16 |
> > - What should be cleaned up after fetching ? |
| 17 |
> |
| 18 |
> These are all the same question, which does take a second to google, |
| 19 |
> but isn't all that time consuming. |
| 20 |
|
| 21 |
Manual stuff isnt that time consuming until you realize it can be |
| 22 |
automated :) |
| 23 |
|
| 24 |
> > - What dirname to use so that it matches ebuilds' $S ? |
| 25 |
> > - What compression to use so that it matches SRC_URI ? |
| 26 |
> |
| 27 |
> cat Manifest |
| 28 |
|
| 29 |
not really |
| 30 |
|
| 31 |
> |
| 32 |
> But seriously, once you've googled the repo, you might notice that |
| 33 |
> it's hosted at github, and that you don't need to create your own |
| 34 |
> snapshot tarballs any more. Want a snapshot from 20150423? Try, |
| 35 |
> |
| 36 |
> https://github.com/pathscale/libcxxrt/archive/665b0223ee27547175dc327a386fcd88243c7677.tar.gz |
| 37 |
> |
| 38 |
> Put COMMIT=665b0223ee27547175dc327a386fcd88243c7677 in the ebuild, |
| 39 |
> stick that in $SRC_URI and $S, and then future snapshots will work |
| 40 |
> without modification. |
| 41 |
|
| 42 |
that might be better, but how do you map date / $PV to commit ? |
| 43 |
|
| 44 |
remember, we want ebuilds that are as much as possible |
| 45 |
version-agnostic, otherwise it breaks simple copy of ebuilds to bump a |
| 46 |
version... |
Archives