<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<i>Isn't it time to change the subject line<br>
Roger<br>
</i>
<blockquote cite="mid:4ED16DC4.20205@sapience.com" type="cite">
<pre wrap="">On 11/26/2011 05:31 PM, Rahul Sundaram wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 11/27/2011 03:50 AM, Genes MailLists wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Try this instead:
rpm -q --whatprovides /usr/bin/growisofs
dvd+rw-tools-7.1-5.fc14.x86_64
(this is on F15 - for some reason I have never understoon - some
packages dont get rebuilt and/or repackages ... )
</pre>
</blockquote>
<pre wrap="">
Simple: Packages don't rebuilt unless there is a necessity to do so
Rahul
</pre>
</blockquote>
<pre wrap="">
Ok - simple, well fine, but beyond the obvious "duh" here, define
necessity please? (Rhetorical)
How do you (or maintainers) know with certainty that there isn't a
header file dependence, or a compiler change that would lead to a faster
(or a bug for that matter).
Is that a necessity if someone has verified working functionality of
an older binary - no probably not - (tho I have no idea if such testing
occurs) but it will lead to bugs being found sooner and any benefits
from compiler improvements etc being taken advantage of. And frankly,
its a bad operational decision to defer full builds.
Further - it just plain 'looks' better for f15 packages to be called f15.
Necessity? Probably not - is it a good idea to wait until a problem
occurs as the decision to rebuild - also probably not.
One man's simple is another man's food for thought.
</pre>
</blockquote>
<br>
</body>
</html>