Re: [isabelle-dev] Haskabelle unmaintained

[Lawrence Paulson]

Deleted from Cambridge.
Larry

> On 9 Dec 2017, at 12:16, Makarius  wrote:
> 
> Since the mirror rsync procedure is conservative by default, the other
> mirror sites should also remove haskabelle.html manually.

___
isabelle-dev mailing list
isabelle-...@in.tum.de
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev

[isabelle-dev] Haskabelle unmaintained

[Florian Haftmann]

Hi all,

I see that the old Haskabelle website is still a regular part of the
Isabelle website: http://isabelle.in.tum.de/haskabelle.html

Since Haskabelle is no out of maintainance it is outdated and should be
removed.  What is the recommended procedure for this?

Cheers,
Florian

-- 

PGP available:
http://isabelle.in.tum.de/~haftmann/pgp/florian_haftmann_at_informatik_tu_muenchen_de



signature.asc
Description: OpenPGP digital signature
___
isabelle-dev mailing list
isabelle-...@in.tum.de
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev

Re: [isabelle-dev] Haskabelle

[Makarius]

On 13/10/16 09:52, Makarius wrote:
> What is the maintenance status of Haskabelle?
> 
> There is still at least one open point concerning the new "isabelle
> process" wrapper and discontinuation of the old $ISABELLE_PROCESS.
> 
> See also
> 
> 
> http://isabelle.in.tum.de/repos/haskabelle/annotate/b885ee4618d8/lib/mk_adapt#l57
>   http://isabelle.in.tum.de/repos/isabelle/rev/cd266473b81b

I have spent 30min trying to make sense of the Haskabelle makedist and
lib/regression process. My impression is that it is generally lagging
behind GHC updates, although I am not proficient with that.

So for now (Isabelle/9ee2480d10b7) the old Haskabelle-2015 is ignored.


If it is updated on time during November, it can be still included in
Isabelle2016-1. If not, there is another chance to publish it as
independent Isabelle component. If that also does not come to pass,
Haskabelle will get lost in time and space -- the usual fate of tools
that are not fully integrated into the Isabelle repository and
development process.


Makarius


___
isabelle-dev mailing list
isabelle-...@in.tum.de
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev

[isabelle-dev] Haskabelle

[Makarius]

What is the maintenance status of Haskabelle?

There is still at least one open point concerning the new "isabelle
process" wrapper and discontinuation of the old $ISABELLE_PROCESS.

See also


http://isabelle.in.tum.de/repos/haskabelle/annotate/b885ee4618d8/lib/mk_adapt#l57
  http://isabelle.in.tum.de/repos/isabelle/rev/cd266473b81b


Is there a deeper reason, why Haskabelle is not part of the main
Isabelle repository? Things outside of that tend to fall into decay.


Makarius
___
isabelle-dev mailing list
isabelle-...@in.tum.de
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev

[isabelle-dev] Haskabelle test

[Lars Noschinski]

Hi,

Is there anyone who knows how the Haskabelle test is setup and can
change it so it runs not only if the Haskabelle repository changes, but
also if the Isabelle repository changed?

  -- Lars
___
isabelle-dev mailing list
isabelle-...@in.tum.de
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev

Re: [isabelle-dev] Haskabelle test

[Florian Haftmann]

 Is there anyone who knows how the Haskabelle test is setup and can
 change it so it runs not only if the Haskabelle repository changes, but
 also if the Isabelle repository changed?

I guess you are referring to the Haskabelle test inside mira.  As far as
I remember, this is the behaviour of the mira scheduler, but my memory
is very dim.  The most clear hints maybe can glimpsed from the mira source.

Hope this helps,
Florian

-- 

PGP available:
http://home.informatik.tu-muenchen.de/haftmann/pgp/florian_haftmann_at_informatik_tu_muenchen_de



signature.asc
Description: OpenPGP digital signature
___
isabelle-dev mailing list
isabelle-...@in.tum.de
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev