Hello Barry, so, libpeas-1.0-0-python2loader has officially made it into Debian. I'm now thinking how to deal with that for roger.
On 03.04.2016 05:35, Barry Warsaw wrote: > On Apr 02, 2016, at 10:33 PM, Rolf Leggewie wrote: > > Hi Rolf, > >> I'm still at a loss what it is you are asking of me. The title of this >> bug requests me to add a run-time dependency that doesn't even exist in >> Debian yet. In Ubuntu the change you advocate has been made, but >> apparently there were no changes necessary for roger-router alongside. >> In fact, roger-router in Ubuntu still depends on libpeas-1.0.0 and not >> libpeas-1.0-0-python2loader even though the package does exist there. > We should certainly fix roger-router in Ubuntu; I'm not sure how I missed that > one over there. I'll file a bug and fix that early next week. Ubuntu is still unchanged both in Xenial and Yakkety. The title of this ticket suggests I should add an explicit dependency on libpeas-1.0-0-python2loader to Depends. I'm a bit reluctant to do that since it would mean I need to maintain a fork since my main computer is trusty. In any case, roger does not ship any python code at all. My understanding is that it uses peas to allow third party plugins and those could be written in python or other programming languages. I'm actually not aware of any plugins and they could be written in either python 2 or python 3. Adding a strong dependency to the python 2 loader seems wrong to me. I feel like adding a Suggests for "libpeas-1.0-0-python2loader|libpeas-1.0-0-python3loader" would be more appropriate. Or should I be mistaken? If it really needs to be a Depends wouldn't it be better to have debhelper and dh_shlibs take care of doing the right thing? Regards Rolf
