On 01/05/2012 10:22 AM, Makarius wrote:
I think one could publish ~isabelle/contrib_devel via HTTP, although
it would require some clean up and tuning, say to expand symlinks.
Another question is how to export the actual directory structure,
without maintaining explicit index.html and tar.gz
On Sun, 8 Jan 2012, Alexander Krauss wrote:
On 01/05/2012 12:19 PM, Jasmin Christian Blanchette wrote:
We are not allowed to distribute Yices. When publishing the components,
please exclude Yices.
... and Vampire.
Could we instead provide a little script (or Isabelle tool) that turns a
Hi all,
here my thoughts on the discussion:
a) release candidates – the announcements of release candidates indeed
could be a device for early feedback. The question is how to incite
users to take them more seriously.
b) development snapshots – I would prefer to get rid of them, providing
Quoting Alexander Krauss kra...@in.tum.de:
However, some components do not come with the release (vampire,
yices, jedit_build). Should we simply have a directory at TUM which
is served via http and where developers can get components? Maybe
simply serve /home/isabelle/contrib_devel for that
