<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 13, 2015 at 2:25 PM, Yaniv Bronheim <span dir="ltr"><<a href="mailto:ybronhei@redhat.com" target="_blank">ybronhei@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>We currently manage debian packaging files under <a href="https://gerrit.ovirt.org/#/q/project:releng-tools" target="_blank">https://gerrit.ovirt.org/#/q/project:releng-tools</a> instead of in the project itself. imo it makes it harder, as developer won't update the debian folder while changing spec parts , which makes much more observation work for Simone..<br></div><div>But if we keep to manage debian that way we should remove the debian folder from <span style="font-size:12.8px">cpopen, vdsm, pthreading to avoid duplication.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Simone can you explain more how you manage to flow code changes and update the debian support currently? should I indeed drop the current debian code that we have in vdsm?<span class="HOEnZb"><font color="#888888"><br clear="all"></font></span></span><span class="HOEnZb"><font color="#888888"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12.8px"><b>Yaniv Bronhaim.</b></span><br></div></div></div></div></div>
</font></span></div></div>
</blockquote></div><br>Issue with keeping debian subdir within the package itself is that it's totally useless unless maintained.</div><div class="gmail_extra">When a new release is issued just tagging the code won't be enough anymore because debian changelog expect to be updated with the release version. So tagging vdsm-4.17.14 without having 4.17.14 in the changelog will cause the package to fail the build (while rpm just issue a error in rpmlint... )</div><div class="gmail_extra"><br></div><div class="gmail_extra">having a separate repo decouple the distribution packaging from the package itself and make it easier to handle at release time.</div><div class="gmail_extra"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>