Re: python packaging, egg-info file vs. directory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Toshio Kuratomi wrote:
Thomas Moschny wrote:
Hi!

Recently encountered a problem with the python-demjson rpm I maintain:
The demjson package does not use setuptools, so, in accordance with
the python packaging guidelines, I used the trick of preloading
setuptools prior to executing setup.py, for F7 and F8 only. This
produces an egg-info directory, fine.

Now, for F9, egg-info is generated automatically, but it turns out
that this produces an egg-info file instead of an directory. This in
turn causes problems when upgrading from F8 to F9, because rpm can't
replace a dir with a file.

Any advices on how to solve this?


Do you have a reason to need eggs on F7 and F8?

Thats strange, I thought it was added because of policy as opposed to reason.  Firstaidkit has no need for eggs, but the reviewer insisted on adding to them.  FWI, firstaidkit chooses to handle the plugins with rpm, which is a valid alternative to eggs.


If not, then the answer is simply to not provide eggs on F7 and F8. Note: If you've already pushed out packages for F7 and F8 you'll need to wait until the next upstream release to make this change.

-Toshio


--
Joel Andres Granados

--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux