<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>There was also a discussion of the piraha-everywhere branch.
Frank</p>
<p>reported that it worked for him without trouble for his non-ET
thorns.</p>
<p>Peter has privately reported the same to me. Frank said he plans
to</p>
<p>go over the patch and understand it in more detail when he gets
back</p>
<p>to the office.<br>
</p>
<p>Cheers,</p>
<p>Steve<br>
</p>
<br>
<div class="moz-cite-prefix">On 08/22/2016 10:31 AM, Roland Haas
wrote:<br>
</div>
<blockquote
cite="mid:20160822103150.3cc61559@8992d193.ncsa.illinois.edu"
type="cite">
<pre wrap="">Present: Erik, Steve, Roland, Frank, Peter, Ian
Formaline:
* Formaline seems very slow, we suspect this to be due to either larger
files being added to tarballs and/or Roland's change that circumvents
gits internal caching
* suggested solutions include undoing the commit and trying to work
around file systems that do not support hard links as well as
tighter integration of Formaline with the flesh make targets to
start Formaline's processing early
* Formaline misses adding Makefile to the tarball, a workaround is to
tar up the flesh repo directly by first de-referencing Makefile (if
it is a symbolic link), then including the directory containing that
file in the tarball. This should work for common situations
Having a moving release branch:
* Roland had suggested having a moving release branch so that eg
websites could refer to that branch rather than having to be updated
after each release, the hope is also to offer a simpler update path
than "wipe your old Cactus tree and download a new one"
* a suggestion is to only have such a branch in the manifest repo and
nowhere else
* Ian dislikes the idea of a moving branch since he fears it will
interact badly with git pull
* Erik points out that git pull will report conflicts if the release
branch jumps from one release to the next and suggests to use a tag
instead, Roland thinks this will not happen and will test this with
locally and report back
* having a simpler way to point to the current release is agreed to be
nice but no simple way to achieve this seems obvious
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a>
<a class="moz-txt-link-freetext" href="http://lists.einsteintoolkit.org/mailman/listinfo/users">http://lists.einsteintoolkit.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>