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

[Florian Haftmann]

>> Common favorites like
>>
>>  if [[ -z "$ISABELLE_IDENTIFIER" ]]
>>  then
>>    ISABELLE_OUTPUT="$ISABELLE_HOME/heaps"
>>    ISABELLE_BROWSER_INFO="$ISABELLE_HOME/browser_info"
>>  fi
>>
>> then could go to
>>
>> f) Admin/etc/settings
> 
> I didn't know that this is still a favourite. I've discontinued this
> scheme when we stopped using cvs.  Settings give a lot of freedom, but
> that should be exercised privately.

Concerning me, I am still working with multiple Isabelle repositories on
the same machine, so I need separate storages for the heaps etc..  I
also do not know what other developers are doing.

This however is only an example for a much general proposal: to figure
out how we can exploit existing Isabelle mechanisms (here, the
components) to provide common infrastructure for developers to bridge
the gap between a raw repository and a compiling repository.  In my
opinion, the more infrastructure is shared (among developers and
automated tests also), the easier it is for newcomers to get acquainted
with it, and the less misunderstandings due to inappropriate setups
(wrong jdk, wrong scala) are likely to appear.

	Florian

-- 

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://mailman46.in.tum.de/pipermail/isabelle-dev/attachments/20120616/137330bf/attachment.sig>