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