<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 2, 2014 at 1:15 PM, Donald Stufft <span dir="ltr"><<a href="mailto:donald@stufft.io" target="_blank">donald@stufft.io</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>I’m pretty sure all the distros have some equivalent to it, often times with similar syntax.</div>
</div></blockquote></div><br></div><div class="gmail_extra">e.g. look here  <a href="https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Package_Versioning">https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Package_Versioning</a></div>
<div class="gmail_extra">yes there's a parallel to our post-releases, namely "Post-Releases", but I don't see a concept for local patches of rpms.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">
to be clear to Daniel, I'm not asking how to package a "local version" of a python package.  that's straightforward (I think) because that's all contained in the "version" segment of the rpm.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">e.g., I recently created an rpm for virtualenv-1.11.4, because centos6 didn't have it yet:  python-virtualenv-1.11.4-1.el6.noarch.rpm</div><div class="gmail_extra">
what's the proper way to "localize" this to not conflict later when 1.11.4 is packaged?</div><div class="gmail_extra"><br></div><div class="gmail_extra">again, sorry for the off-topic post, but I was *hoping* Nick (or someone) would have the concept handy from the OS packaging world.</div>
<div class="gmail_extra"><br></div></div>