[Rpm-maint] incompatible pythoneggs deps generator merged

Thierry Vignaud thierry.vignaud at gmail.com
Tue Sep 1 13:41:32 UTC 2015


Hi

I see that you've merged pythoneggs generator in rpm.org:
http://rpm.org/gitweb?p=rpm.git;a=log;h=ce15157774833c81f9610693ffffb1473556f8cd

I would suggests merging Mageia's one instead:
http://gitweb.mageia.org/software/rpm/rpm-setup/plain/pythoneggs.attr
http://gitweb.mageia.org/software/rpm/rpm-setup/plain/pythoneggs.py

Rationale:
- it's plugged it with the internal deps generator;
- it works with the internal deps generator
- it doesn't mix typelib() deps with pythoneggs() ones[1]
- it doesn't rely on a non existent gi-find-deps.sh script[1]
- it's well tested with rpm.org as we used it for a couple years
whereas the one imported is just one that was used with rpm5.

Also currently that would make rpm-4.13 break deps on Mageia Linux
(b/c of pythoneggs(3) vs python3egg deps) whereas if Per Oyvind's
distro switches from rpm5 to rpm.org, they'll need mass rebuild b/c of
all the changes between rpm5 & rpm.org, so I think they could afford
migration from pythonXegg() to pythoneggs(X)()

What's more, this commit suggests that it actually changes the deps
style against what's currently used by them currently with rpm5:
http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=3523921ea9366746623bb634c5d304c258e67354

So the less intrusive change would be to stick with Mageia pythoneggs(x) style:
It would be useless & gratuitous to break deps for Mageia when the
distro that's thinking about switching from rpm5 to rpm.org will
actually have to switch deps style already.
It's better to have only one distro to switch deps style rather than
two, isn't it?

What's more, from what I've read on the cooker ml, the switch to
rpm.org hasn't been agreed yet, it's just a proposal.
So that's one more reason for not breaking Mageia

My 2 cents

Summary: Please do not break Mageia
Thanks

See you

[1] if we merge typelib() generators, please bring in the Suse guys
are they're the ones who write it and we're using their version too.
Please stick which was is used by current rpm.org users instead of
what's may used by a distro which might switch from rpm5 to rpm.org
(which doesn't seem decided yet)


More information about the Rpm-maint mailing list