[MAGEEC] BEEBS 2.0 Release Branch

[Alex J Lennon]

On 05/09/2014 12:54, George Field wrote:
> Hi Andrew,
>
>     I don't know if we have anywhere to place a release .tar.gz package,
>     so for now all I propose is an announcement to this mailing list,
>     including instructions on how to download and create a release
>     package.
>
>
>  GitHub has a releases system
> <https://github.com/blog/1547-release-your-software> that is backed by
> Git tags - they allow you to attach a binary that is made available to
> the public. Perhaps that's the best way to host a tarball?
>

fwiw. Small thing but I was using this technique for some embedded work
with Yocto and ran into trouble. The release archives can be recreated
behind the scenes which means that checksums can (and do) change
intermittently.

This might not be relevant for BEEBS releases, but if you care about
ensuring that any given release archive never changes then the
alternative is to take an additional step of uploading the archive to
GitHub yourself, in which case the site won't make any changes to that file.

Cheers,

Alex


> As an aside - if anyone knows how to fix #26, we probably want to
> patch that up before it's included in a release.
>
> Cheers,
> George
>
>
> _______________________________________________
> mageec mailing list
> mageec at mageec.org
> http://mageec.org/cgi-bin/mailman/listinfo/mageec


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mageec.org/pipermail/mageec/attachments/20140905/d44d19d7/attachment.html>