Open Stack

On Mon, Jan 13, 2014 at 3:41 PM, Kevin L. Mitchell <
kevin.mitchell at rackspace.com> wrote:

> On Mon, 2014-01-13 at 12:07 -0500, Doug Hellmann wrote:
> > We can't just compute the hash of the modules in the project receiving
> > copies, and then look for them in the oslo-incubator repo, because we
> > modify the files as we copy them out (to update the import statements
> > and replace "oslo" with the receiving project name in some places like
> > config option defaults).
>
> Why not embed the hash into the files as we copy them out, maybe as a
> specially formatted comment at the end of the file?
>

The problem is much much easier for the second update. The real challenge
is getting the first update right, when we don't know what the initial hash
is.



>
> That said, I've always thought that oslo-incubator should be a library
> we use directly, rather than a repository we copy out of.
>

We're working on that. That's another reason I don't really want to spend
a lot of time making update.py fancier -- it takes away from time I could
be spending on making the code into libraries in the first place.

Doug



> --
> Kevin L. Mitchell <kevin.mitchell at rackspace.com>
> Rackspace
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140113/52d511b9/attachment.html>