<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-04-26 11:24 GMT+02:00 Michael Scherer <span dir="ltr"><<a href="mailto:misc@zarb.org" target="_blank">misc@zarb.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le vendredi 25 avril 2014 à 19:30 +0200, Miloslav Trmač a écrit :<br>
<div class="">> For LSB, there is an explicit promise that if a vendor does what is<br>
> specified, the package will be possible to install and will run<br>
> correctly. We do, of course, have the option to repudiate LSB and<br>
> explicitly say we don't care for future releases.<br>
<br>
</div>So shouldn't redhat-lsb or some subpackage be the one that pull that<br>
part ?<br></blockquote><div><br></div><div>That's a clean solution for the LSB concern, but not for the larger point. (Honestly this is more a matter of reinforcing the principle than finding a perfect solution for that specific file.) <br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> And it's not only commercial software; private projects that make no<br><div class="">
> sense to publish (such as a company's web site) are equally affected<br>
> such changes. Simply spoken, if we care only about package in Fedora,<br>
> we are building an appliance; if we want to build an operating system,<br>
> we do need to cater for software not included directly in the repo.<br>
<br>
</div>Then how can we signal to people that they need to update those<br>
packages ?<br></blockquote><div> <br></div><div>My opinion is that <i>in most cases</i> this is just asking the wrong question; we shouldn't <i>need</i> to signal that. When old applications correctly using the API of $os_name stops working, your product is in a very practical sense <i>no longer $os_name</i>.<br>
</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Because we can as well say "we are gonna support that forever", but that<br>
will result into bitrot if no one really test.<br></blockquote><br></div>The principled answer to this is to have a comprehensive automated test suite... which, unfortunately, we don't have.<br></div><div class="gmail_extra">
Mirek<br></div></div>