I have started investigating packaging rally. One of the problems I'm hitting is
something we also hit (and never, afaik, resolved) when packaging openstack-tempest.
Upstream does not provide a tarball for rally via launchpad, so building a rally RPM
doesn't work quite the same as, say, nova.
In particular, the PKG-INFO file which you get from e.g. nova via launchpad is not present
in the rally 0.0.4 tarball you get from github. This causes pbr to complain that it's
not being run in a git repo and it can't figure out versioning.
I've worked around this in my poc spec/rpm by patching in a 'dummy' PKG-INFO
file (which I cut-n-pasted from nova).
Two questions for this group.
1) What do we think of this approach of including a fabricated PKG-INFO file to define the
version info for pbr et al?
2) If we like this idea, how does this fit in with delorean? IIUC, going forward we want
to avoid using midstream repos. What about using
https://github.com/openstack/rally as the
upstream and something in
github.com/redhat-openstack as a patches branch containing the
PKG-INFO file alone? I guess what I'm asking is where should we maintain a PKG-INFO
file of our own creation. Maybe where we keep the spec?
Thanks in advance for your thoughts.
Steve Linabery (freenode: eggmaster)