On 08/03/2013 12:46 PM, Fotis Georgatos wrote: > Hello EasyBuilders, > > > > 3) obtaining existing and new application sources > > Life has it, that developers don't always have an understanding of what it > means > to run HPC operations and play tricks around software distribution channels, > ranging from non-tagging a git repo (benign) up to flatly swapping tarballs > (annoying): > see https://github.com/hpcugent/easybuild-easyconfigs/pull/374/files > > Especially modifying the release channel mid-flight, is a big hassle; I did > spend > an extra few hours to understand why Rgputools PR arrived broken on github: > :-( > https://github.com/hpcugent/easybuild-easyconfigs/pull/282 You do realise you don't need a tag in github, you can also use https://github.com/ekg/fastahack/archive/23c2b7176b601cf1b326a8e6b6817dc0ae6ce29c.tar.gz <https://github.com/ekg/fastahack/archive/23c2b7176b601cf1b326a8e6b6817dc0ae6ce29c.zip> for any commit id.
> > In short, let's pool our tarballs together in some way, > define preferred release streams and avoid these issues re-occuring. > Bioinfo toolchain is especially prone to this, due to the many small tools. Another way would be to put everything on github, and use this for our mirroring, we can fork existing projects that are already on github, and upload sources from freely attributable software to some central repo. That is, we quickly need github support in easybuild then. :-p Regards Jens Timmerman
