[isabelle-dev] Future and maintainance of ~isabelle/contrib_devel at TUM NFS

[Christian Sternagel]

Dear Florian,

I noticed that the following components are required (due to 
Admin/components)

cvc3-2.2
e-1.5
hol-light-bundle-0.5-126
kodkodi-1.2.16
spass-3.8ds
scala-2.9.2
vampire-1.0
yices-1.0.28
z3-3.2
jedit_build-20120414

of which

e-1.5 (instead there is e-1.4)
hol-light-bundle-0.5-126
vampire-1.0
yices-1.0.28
jedit_build-20120414

are not available from http://isabelle.in.tum.de/dist (of those, at 
least jedit_build should be not non-free, I guess).

cheers

chris

On 06/27/2012 05:46 AM, Florian Haftmann wrote:
> Tiny instructions on changesets c97656ff4154 ff.:
>
> * include the following snippet into your ~/.isabelle/etc/settings:
>
>      source "${ISABELLE_HOME}/Admin/init_components"
>
> * obtain components from Isabelle2012, http://isabelle.in.tum.de/dist or
> nfsbroy:/home/isabelle/contrib; hints which components are still missing
> can be obtained by a simple isabelle call (e.g. `isabelle getenv)
>
> * try whether it works, e.g.
>
>      isabelle jedit -bf
>
> This is just a first start and required further thought:
> * Will the idea of platform-universal components revived?  If yes, the
> platform-sensitive components files can be discontinued.  I personally
> like the idea, though?
> * How to deal with the non-free components?  Once a solution is found
> there, components can be required strictly, not liberal.
> * Use this mechnisms uniformly in mira and isatest.
> * Cleanup and maintainance of nfsbroy:/home/isabelle/contrib
> * Should Admin/ become a component in itself?
> * …
>
> Happy hacking,
> 	Florian
>
>
>
> _______________________________________________
> isabelle-dev mailing list
> isabelle-dev at in.tum.de
> https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
>