<br><br><div class="gmail_quote">On Sat, Mar 5, 2011 at 1:50 PM, Alexandre Prokoudine <span dir="ltr"><<a href="mailto:alexandre.prokoudine@gmail.com">alexandre.prokoudine@gmail.com</a>></span> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
So what you are saying is that we will never be able to do it :)<br>
<br>
</blockquote><div><br></div><div>Oh come on, you should know me at least well enough to know I don't believe that and certainly didn't say it:)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I heartily disagree. Tweaking OS to get things done comes *before* you<br>
start meddling with Ardour and isn't required all the time.</blockquote><div><br></div><div>The problem is that most of the time it is.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
That makes<br>
it possible to just write an Appendix that will cover several<br>
distributions, while bloody well focusing on Ardour. So what's the<br>
problem?<br>
<div><div class="h5"><br>
</div></div></blockquote><div><br></div><div>In that case you are writing a manual for Ardour, so wanna join the work already in progress that you just wrote about?;)</div><div><br></div></div><div>Of course the appendixes would require constant maintenence and would be exceedinly numerous as there are numerous distributions used in pro audio on Linux. That, I think but am not certain, is why the FLOSS manual covered Ubuntu to a limited degree and left it there. Trying to cover all of them is quite challenging and requires much more time than they had.<br>
</div><div><br></div><div>Of course that being said just triyng to cover all of what Ardour can do is challenging in itself, trust me:)</div><div><br></div><div> Seablade</div>