On 09/01/2015 05:03 PM, Andy Grover wrote: > 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
Andy, Ok, so basically, I have nothing to do, but to package the last version of rtslib-fb. Am I right? If so, then I'll package rtslib-fb ASAP in Debian Experimental. Please let me know if the new version would also work with Kilo (in which case, I'd upload to Debian Sid rather than Experimental). As for the transition period, I'd suggest to keep it transitioning for Liberty, and as soon as Liberty is out, just remove the old rtslib folder in the favor of the new rtslib-fb. Your thoughts? Cheers, Thomas Goirand (zigo)
