On Wed, Mar 31, 2010 at 8:10 PM, james anderson <span dir="ltr">&lt;<a href="mailto:james.anderson@setf.de">james.anderson@setf.de</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word;">
in general, &quot;image-driven&quot; development does not preclude a release which comprises more that one file, but if you were more specific about requirements, it would be easier understand where the problems arise for ecl.</div>
</blockquote><div><br>I have written a very very long email after this one. Read it. Software can be built with ASDF without needing it to run. We can deliver FASL files that can be used for people that do not use or do not have ASDF installed<br>
 </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;"><div><div>there was a concern expressed that a program be able to locate components at all stages in its life-cycle. the concern predates asdf. the mechanism to accomplish it as well. they can be integrated with asdf, used along side it, or used independently. it is demonstrably possible to do any and all.</div>
</div></div></blockquote><div><br>Yes, frack! Have I said that I want to replace ASDF? No! You all seem to read just words and not get the global idea.<br><br>I have written probably now 5000 words claiming that ASDF can accomodate ALL PARADIGMS.<br>
I have repeated this about 50 times now.<br>I have provided extensions to include THOSE ways of working.<br>I have suggested minor changes that help in the task -- logical pathnames for program delivery.<br>I have even suggested extensions to integrate ASDF with other build processes -- asdf-install, asdf-build<br>
<br>And all I get is a request for more more and more writing.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;">
<div><div>neither of these issues is necessarily related with a &quot;image-driven&quot; development paradigm.<br></div></div></div></blockquote></div><br clear="all">It is related, in the sense that you are all so focused on the load, load, load, maybe dump process that  that nobody here cares a penny about other models. And this causes a lot of friction and resistance against anything that may break your workflow -- which I insist is not my goal.<br>
<br>This is getting so tiresome that I may just as well quit and forget.<br><br>Juanjo<br><br>-- <br>Instituto de Física Fundamental, CSIC<br>c/ Serrano, 113b, Madrid 28006 (Spain) <br><a href="http://tream.dreamhosters.com">http://tream.dreamhosters.com</a><br>