<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 16, 2015 at 2:41 PM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
we've setup our doc repositories so that the dependencies are the same as described in the global-requirements.txt file that is part of the requirements project.<br>
<br>
This gives us two things:<br>
1) Syncing of updates to all our repos<br>
2) Syncing of requirements across repos<br>
<br>
Anne and myself often have a hard time getting changes into the requirements repository.<br>
<br>
So, I came up with exposing the soft flag to the update process. The soft flag allows to update a project without touching or complaining about files that are not in the global-requirements.txt file:<br>
<a href="https://review.openstack.org/#/c/173200/" target="_blank">https://review.openstack.org/#/c/173200/</a><br>
<a href="https://review.openstack.org/#/c/173201/" target="_blank">https://review.openstack.org/#/c/173201/</a><br>
<br>
But I wonder whether all this is worth it and we should not remove our repositories from requirements.<br>
<br>
The primary use case of requirements is to make installation of projects possible with sharing common requirements.<br>
<br>
It's nice that you can install the doc tools on these machines as well but not a hard requirement.<br>
<br>
It's nice that we can change one place - global-requirements.txt - and then the proposal bot updates everything.<br>
<br>
But it's not a necessity to have it.<br>
<br>
I'd like to have your advise on how to continue:<br>
a) Continue as we do today<br>
b) Use the soft updating as my two patches aboe<br>
c) Remove our repos from projects.txt of the requirements repo<br>
<br>
If we go with c, keep in mind that our tool openstack-doc-tools will stay in the global-requirements.txt file since it's used by the trove project which is the only project that builds DocBook XML documents using our toolchain,<br></blockquote><div><br></div><div>If we continue as we are today, do we get the same requirements for building docs as for building the rest of OpenStack? Yes, and that's important.</div><div><br></div><div>I think it's fine to go with c) and not add soft flags. However, I don't want to remove all the docs repos from projects.txt of requirements. I do think that for each release we want to indicate which version of openstackdocstheme to use to build. Does that sound do-able?</div><div><br></div><div>Thanks!</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Andreas<span class="HOEnZb"><font color="#888888"><br>
-- <br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,<br>
Graham Norton, HRB 21284 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
<br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a></div>
</div></div>