<div dir="ltr"><div><div><div><div><div><div><div><div>Hi Filippo, <br><br></div>I agree, this is something that needs to be discussed at some point to ensure viability of the project.<br><br></div>Coming back to the install/makedeps.sh script, there is a problem. <br><br></div>The problem is that the script is need before "make" but also rely on "make". <br><br></div>Indeed, the only way to make it work is to do the following:<br><br>------------------------------------------------------------------<br><div>make veryclean<br></div><div>./configure<br></div><div><br></div>make -C Modules version <br><div><br>cd install;gzip -dc ../archive/iotk-1.2.beta.tar.gz | (cd ../; tar -xvf -)<br>cp iotk_config.h ../S3DE/iotk/include/iotk_config.h<br clear="all">cd ../; ln -fs S3DE/iotk iotk<br><br></div>sh install/makedeps.sh<br>-----------------------------------------------------------------<br><br></div>Therefore those lines should be included either in the configure or in the install/makedeps.sh script. <br><br></div>I can commit the change if you wish? Would you prefer to have that in "configure" or in "makedeps.sh" ?<br><br></div>Best, <br><br></div>Samuel & Martin<br><div><div><div><div><div><div><br><div><div><div><br></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 28 March 2016 at 16:56, Filippo Spiga <span dir="ltr"><<a href="mailto:filippo.spiga@quantum-espresso.org" target="_blank">filippo.spiga@quantum-espresso.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Samuel,<br>
<span class=""><br>
On 28 Mar 2016, at 16:18, Samuel Poncé <<a href="mailto:samuel.pon@gmail.com">samuel.pon@gmail.com</a>> wrote:<br>
> Concerning the limitation of the number of commits, I guess the problem is that the .svn history starts to be huge.<br>
<br>
</span>I do not see a problem here, "huge" in term of number of commits or "huge" in term of space? For the second case, there are bigger SVN repositories on QE-FORGE. "q-e" is ok-ish.<br>
<br>
A fresh SVN checkout takes time but a fresh GIT clone is way faster. The GIT mirror simplifies a lof of network operations because of the way GIT is engineered compared to SVN. I had a proposal for mixed SVN-GIT that can be a candidate solution to avoid "waterfall commits" but it requires people to change a bit their way of contributing and a more pro-active way of branching and merging.<br>
<span class=""><br>
<br>
> There is also the problem of qe-forge being temporarily inaccessible after a commit (this one is weird).<br>
<br>
</span>I wish I can tell why this happen, I suspect it is a hook script in the current QE-FORGE that has been activated automatically while doing cleaning routine operations on the server side. The problem may naturally disappear when we move to a new QE-FORGE portal. No ETA is defined yet but it must happen before September.<br>
<span class=""><br>
<br>
> A suggestion might be to restart clean at the next major QE release, off course saving the history file somewhere?<br>
<br>
</span>This is something I personally prefer to avoid. During the migration of the SVN repository on the new QE-FORGE we will have the opportunity to delete completely all inactive branches and purge away very old big files stored at the early stages of the repository history. This will make the "size" smaller while keeping full historical record.<br>
<br>
I will discourage the discontinuity of the SVN legacy repository unless drastically changes the collaborative development are applied. IMHO the community is not ready.<br>
<br>
I hope this topic (that is bery important to ensure sustainability of QE project going forward) will be on the agenda of the next plenary QE developer meeting early 2017.<br>
<br>
Cheers<br>
<br>
--<br>
Filippo SPIGA<br>
* Sent from my iPhone, sorry for typos *<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
Q-e-developers mailing list<br>
<a href="mailto:Q-e-developers@qe-forge.org">Q-e-developers@qe-forge.org</a><br>
<a href="http://qe-forge.org/mailman/listinfo/q-e-developers" rel="noreferrer" target="_blank">http://qe-forge.org/mailman/listinfo/q-e-developers</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><span><font color="#888888"><pre cols="72">------------------------------------------------------------------------------------------------
Dr. Samuel Poncé
Department of Materials
University of Oxford
Parks Road
Oxford OX1 3PH, UK
Phone: +44 1865 612789<br> email: <a href="mailto:samuel.ponce@materials.ox.ac.uk" target="_blank">samuel.ponce@materials.ox.ac.uk</a> <a href="mailto:fabio.caruso@materials.ox.ac.uk" target="_blank"></a>
web: <a href="http://giustino.materials.ox.ac.uk/index.php/Site/SamuelPonc%e9" target="_blank">http://giustino.materials.ox.ac.uk/index.php/Site/SamuelPonc%e9</a>
------------------------------------------------------------------------------------------------</pre></font></span></div></div>
</div>