<div class="gmail_quote">2010/5/22 Toshio Kuratomi <span dir="ltr"><<a href="mailto:a.badger@gmail.com">a.badger@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="im">On Sat, May 22, 2010 at 02:03:06AM +0545, Drak wrote:<br>
> I was asking how do we let Fedora know if we have applied a vendor patch to our<br>
> distro that has not yet been released by the vendor in an official version but<br>
> will be part of their next release (some when). Is there an official way to<br>
> let you know what the patches are? Possibly just a notice in our readme<br>
> sighting vendor versions and or revision numbers from their VCS?<br>
><br>
</div>I'm not sure what all your referencing:<br>
* Who is we?<br>
* What is our distro?<br>
* Who is the vendor?<br>
* Who is the you that you're letting know?</blockquote><div><br></div><div>Ok plain English time :-P</div><div>When we Zikula need to add a vendor patch for a vendor library we distribute with Zikula, we Zikula need to let you know what the vendor patch is so your packagers know what to patch. How do we let you know what the correct patch is officially. Vendor patch means a patch committed to their VCS but not yet released in an official version.</div>
<div><br></div><div>e.g. Zikula uses Smarty. Smarty fixes something important to us, but hasnt yet released a version that includes that fix. So we checkout revision X from their source control or file y from revision X and patch the version of Smarty we distribute. How do we let you know if we have in fact needed to do this.</div>
<div><br></div><div>This particular example is fictitious but the way, but could very well happen.</div><div><br></div><div>Drak</div><div><br></div></div>