<div bgcolor="#FFFFFF" text="#000000">
On 08/20/2011 11:22 PM, Jon Ciesla wrote:
<blockquote type="cite">
<pre></pre>
<blockquote type="cite">
<pre>On 08/20/2011 11:08 PM, Jon Ciesla wrote:
</pre>
<blockquote type="cite">
<pre>No, I'm not. The files vavoom would want the user to download are not
owned by the vavoom package, they're in the user's ~, are they not?
</pre>
</blockquote>
<pre>I am talking about doom-shareware.desktop and doom.autodlrc and you are
talking about the data it downloads
</pre>
</blockquote>
<pre>Right. I'm saying each RPM could have it's own versions of those two
files, which use the same paths in the user's ~<br><br></pre>
</blockquote>
<blockquote type="cite">
</blockquote>Now we are going in a bit of a circle. To reiterate what I asked in the first mail, I am asking if there is a better alternative to just duplicating these files? Why? Because I just built a vavoom update and had to fix doom.autodlrc because one of the mirrors was not valid anympore. Now if there are multiple engines packaged, such a fix would have to be propagated across three or more packages depending on how many "ports" aka different doom engines gets packaged. <br>
<br>Rahul<br>
<br>
</div>