On 17 November 2015 at 00:38, Neal Gompa <ngompa13(a)gmail.com> wrote:
Hello all,
I recently upstreamed some fixes to a new RPM dependency generator
that will be available as an option for distributions to enable. The
new generator uses python .egg data to generate Provides and Requires
in the form of pythonXegg(Y), where X is the Python major version and
Y is the module.
I'm not clear on what you mean by depending on an egg. Eggs are a
binary format that isn't compatible with Linux distro packaging
policies, since they lose too much structural information regarding
where files should be installed for policy compliance - that's one of
the major reasons we defined the wheel format as a next generation
replacement:
https://www.python.org/dev/peps/pep-0427/.
Is the goal to enable installation commands like "dnf install
python3egg(Django)" and have that install the distro's Django package?
If so, then there's some relevant work currently under way upstream to
improve the interaction between Python installation tools and build
systems to improve the metadata extraction process, rather than
relying on implementation details of setuptools.
Regards,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia