<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 8, 2015 at 1:58 PM, Galo Navarro <span dir="ltr"><<a href="mailto:galo@midokura.com" target="_blank">galo@midokura.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Sandro,<br>
<span class=""><br>
>> 1) (Downstream) packaging: midonet and python-midonetclient are two<br>
>> distinct packages, and therefore should have distinct upstream<br>
>> tarballs - which are compiled on a per repo basis.<br>
<br>
</span>This is actually not accurate: there is no such thing as a midonet<br>
package. The midonet repo produces 4 or 5 separate packages: agent,<br>
cluster, tools, py client.<br>
<br>
I'd like to understand a bit better what exactly you're trying to<br>
achieve. Is it to produce tarballs? All of them? Just<br>
python-midonetclient?<br>
<br>
Let's examine the concrete requirements before rushing headlong into<br>
highly disruptive changes like splitting repos. For example, a<br>
py-midonetclient tarball can be built already without having a<br>
separate repo.<br>
<span class=""><br>
> 3) In order to put python-midonetclient on PyPI, it's probably<br>
> required to be in its own repo as well, isn't it? Because that's<br>
> another requirement [3]<br>
<br>
</span>Ditto. We already have a mirror repo of pyc for this purpose<br>
<a href="https://github.com/midonet/python-midonetclient" rel="noreferrer" target="_blank">https://github.com/midonet/python-midonetclient</a>, synced daily.<br></blockquote><div><br></div><div>Some of the problems with that is that it does not have any git log history<br></div><div>nor does it feel like a coding project at all.<br><br></div><div>Allow me to put forward a solution that will allow you keep the development<br></div><div>in the midonet tree while, at the same time, having a proper repository<br></div><div>with identifiable patches in <a href="http://github.com/midonet/python-midonetclient">github.com/midonet/python-midonetclient</a><br><br></div><div>Look at the repo I created [1] and specially at its commit history [2]<br><br></div><div>As you can see, it has all the commit history relevant for the<br></div><div>midonet/python-midonetclient (and only that one) is present.<br><br></div><div>This is generated in the following way. There should be job that does once in the<br></div><div>midonet repo:<br></div><div><br> git format-patch -o "${HOME}/patches_current --relative=python-midonetclient \<br> 7aef7ea7845a2125696303a277d40bd45c9240e2..master<br><br></div><div>Then, each day it should do:<br><br></div><div> cd ${JOB_HOME}<br></div><div> git clone <a href="https://github.com/celebdor/python-midonetclient.git">https://github.com/celebdor/python-midonetclient.git</a><br> git clone <a href="https://github.com/midonet/midonet.git">https://github.com/midonet/midonet.git</a><br> <br> pushd midonet<br></div><div> git format-patch -o "${JOB_HOME}/patches_new" --relative=python-midonetclient \<br> 7aef7ea7845a2125696303a277d40bd45c9240e2..master<br></div><div> popd<br></div><div> pushd python-midonetclient<br></div><div> <br> for file in `diff <(ls -1a "${HOME}/patches_current") <(ls -1a "${JOB_HOME}/patches_new") | cut -f2 -d' '`<br> do<br> git am < "${JOB_HOME}/patches_new/$file"<br> done<br></div><div> <br> popd<br></div><div> mv patches_new "${HOME}/patches_current"<br><br></div><div>It should be quite straightforward to change whichever job you currently use to<br></div><div>this.<br><br></div><div>The last remaining issue will be that of tags. <a href="http://github.com/midonet/midonet">github.com/midonet/midonet</a> is not<br>tagging all the releases. However, python-midonetclient should, so I would just<br></div><div>ask that when you make a release you push the tag to python-midonetclient<br></div><div>as well.<br></div><div><br>[1] <a href="https://github.com/celebdor/python-midonetclient/">https://github.com/celebdor/python-midonetclient/</a> <br>[2] <a href="https://github.com/celebdor/python-midonetclient/commits/master">https://github.com/celebdor/python-midonetclient/commits/master</a><br><br><br></div><div>Regards,<br><br></div><div>Toni<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=""><font color="#888888"><br>
g<br>
</font></span><div class=""><div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>