<p dir="ltr">Another reason to put more stuff in the main tgz is that some (most?) computing centers disallow direct Internet connection from the ssh nodes, which causes the auto download to fail </p>
<p dir="ltr">-- <br>
Lorenzo Paulatto<br>
Written on a virtual keyboard with real fingers</p>
<div class="gmail_extra"><br><div class="gmail_quote">On 18 Aug 2016 10:22 p.m., "Nicola Marzari" <<a href="mailto:nicola.marzari@epfl.ch">nicola.marzari@epfl.ch</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Dear all,<br>
<br>
many times these codes are installed centrally once for all<br>
by a sysad, and users are discouraged to run/compile independently<br>
their own executables - a good policy, if you think.<br>
<br>
Noone suggested an even more baroque set up - my desire was to simplify<br>
things, and I am convinced a single file or a single script<br>
that installs everything would benefit everyone. The argument that it<br>
costs more to download seems just too hard to take - I'm happy to provide<br>
free mirrors where everyone is redirected to at download time.<br>
<br>
<br>
nicola<br>
<br>
<br>
<br>
<br>
<br>
On 18/08/2016 22:05, Layla Martin-Samos wrote:<br>
> Dear all, I agree with Stefano. The present mechanism is simple and only<br>
> thinks that are very general and very core (PW, Modules, install) are<br>
> downloaded. Making a distinction between core , second shell, third<br>
> shell, half shell, made@somewhere or elsewhere ... may be even more<br>
> confusing, and maybe will bring some issues. Moreover, some 'core' (lets<br>
> call it 'historical') are very specific (like neb) and used only in<br>
> particular applications, why to download them by default? at the moment<br>
> if a user wants to use neb, he only needs to type make neb, and that's<br>
> all, like for the other 'packages' irrespectively of who, how, when, why<br>
> and what. boh!<br>
><br>
> cheers<br>
><br>
> Layla<br>
><br>
><br>
> 2016-08-18 11:20 GMT+02:00 Stefano Baroni <<a href="mailto:baroni@sissa.it">baroni@sissa.it</a><br>
> <mailto:<a href="mailto:baroni@sissa.it">baroni@sissa.it</a>>>:<br>
><br>
> Possiamo graduare la distinzione fra pacchetti “core” e gli altri<br>
> (ad esempio distribuendo per default neb.x, ph.x, e pochi altri), ma<br>
> secondo me il meccanismo attuale va mantenuto. SB<br>
><br>
>> On 18 Aug 2016, at 11:13, Filippo Spiga<br>
>> <<a href="mailto:filippo.spiga@quantum-espresso.org">filippo.spiga@quantum-<wbr>espresso.org</a><br>
>> <mailto:<a href="mailto:filippo.spiga@quantum-espresso.org">filippo.spiga@quantum-<wbr>espresso.org</a>>> wrote:<br>
>><br>
>> I am *PERSONALLY* aligned with Nicola's way of thinking. A single<br>
>> package would simplify a lot, including the perception to the<br>
>> public about what QE is and what is part of QE distribution. We<br>
>> can continue to have third-part packages following this<br>
>> "on-demand" model (West? EPW? SaX?) but NEB, PH, TDDFT and others<br>
>> packages that exist since ages can be collected under the same<br>
>> umbrella.<br>
>><br>
>> I have always believed that the reason we had many packages is to<br>
>> avoid a monolithic heavy distribution. Based on what I see, the<br>
>> core source code is not "that big" in size.<br>
>><br>
>> I personally see some beauty and some practicality in changing the<br>
>> packaging process. The 6.0 will continue to follow the current<br>
>> process unless the majority of contributors agree differently. But<br>
>> because 6.0 is going to introduce already some new stuff, I<br>
>> personally think this is a good time to review the packaging<br>
>> process as well.<br>
>><br>
>> Just my 2 cents ...<br>
>><br>
>> On 18 Aug 2016, at 09:51, Stefano Baroni <<a href="mailto:baroni@sissa.it">baroni@sissa.it</a><br>
>> <mailto:<a href="mailto:baroni@sissa.it">baroni@sissa.it</a>>> wrote:<br>
>>> Then we have simply to beat the drum by claiming that our<br>
>>> “virtual” (or whatever fancy adjective you may find) distribution<br>
>>> model is “innovative” and much better than the old-fashioned tar<br>
>>> balls … SB<br>
>><br>
>> --<br>
>> Filippo SPIGA<br>
>> * Sent from my iPhone, sorry for typos *<br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Q-e-developers mailing list<br>
> <a href="mailto:Q-e-developers@qe-forge.org">Q-e-developers@qe-forge.org</a> <mailto:<a href="mailto:Q-e-developers@qe-forge.org">Q-e-developers@qe-<wbr>forge.org</a>><br>
> <a href="http://qe-forge.org/mailman/listinfo/q-e-developers" rel="noreferrer" target="_blank">http://qe-forge.org/mailman/<wbr>listinfo/q-e-developers</a><br>
> <<a href="http://qe-forge.org/mailman/listinfo/q-e-developers" rel="noreferrer" target="_blank">http://qe-forge.org/mailman/<wbr>listinfo/q-e-developers</a>><br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<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/<wbr>listinfo/q-e-developers</a><br>
><br>
<br>
--<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
Prof Nicola Marzari, Chair of Theory and Simulation of Materials, EPFL<br>
Director, National Centre for Competence in Research NCCR MARVEL, EPFL<br>
<a href="http://theossrv1.epfl.ch/Main/Contact" rel="noreferrer" target="_blank">http://theossrv1.epfl.ch/Main/<wbr>Contact</a> <a href="http://nccr-marvel.ch/en/project" rel="noreferrer" target="_blank">http://nccr-marvel.ch/en/<wbr>project</a><br>
______________________________<wbr>_________________<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/<wbr>listinfo/q-e-developers</a><br>
</blockquote></div></div>