<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-04-25 12:40 GMT+02:00 "Jóhann B. Guðmundsson" <span dir="ltr"><<a href="mailto:johannbg@gmail.com" target="_blank">johannbg@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
On 04/24/2014 04:30 PM, Miloslav Trmač wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Only those that are maintained directly inside Fedora.<br>
</blockquote>
<br></div>
Which is what we care about we cannot hold back progress in the distribution based on someone, someplace, somewhere might be using legacy cruff.<br>
<br>
It's better for everybody they themselves included that they maintain those packages or components within Fedora itself or those individuals or company's will need to adapt they themselves to our changes when we make them.<span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote><div><br></div></div>That's certainly an option but it's not the only one; see the recent "Functional" threads for example.<br><br></div><div class="gmail_extra">For LSB, there is an <i>explicit promise</i> that if a vendor does what is specified, the package will be possible to install and will run correctly. We do, of course, have the option to repudiate LSB and explicitly say we don't care for future releases.<br>
<br></div><div class="gmail_extra">And it's not only commercial software; private projects that make no sense to publish (such as a company's web site) are equally affected such changes. Simply spoken, if we care only about package in Fedora, we are building an appliance; if we want to build an operating system, we do need to cater for software not included directly in the repo.<br>
</div><div class="gmail_extra"> Mirek<br></div></div>