On 09/01/2015 04:41 AM, Thomas Goirand wrote:
Hi Andy,
How do you propose that I do what you suggested (ie: package rtslib-fb
with both names available)? Isn't this something you should work out
yourself, as an upstream?
BTW, thanks for solving this conflict. With my package maintainer hat
on, this is very much appreciated.
I haven't found an elegant way to alias package names -- I guess it's
not a very common issue. What I've done is have the upstream setup.py
lists both rtslib and rtslib_fb as packages, and the tarball has
rtslib_fb/ as a symlink to rtslib/. Setup.py builds and installs both.
Importing with the name "rtslib" generates a deprecation warning.
If OpenStack is the only user of rtslib-fb, I just took a look at Cinder
and it appears they've already made the change to try importing
rtslib_fb first! So maybe the transition period where we have both can
be relatively short.
-- Andy
