[Bug 240736] [NEW PORT] astro/py-ephem: ephem has new naming scheme, pyephem is a stub now
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Sep 21 17:35:22 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240736
Bug ID: 240736
Summary: [NEW PORT] astro/py-ephem: ephem has new naming
scheme, pyephem is a stub now
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs at FreeBSD.org
Reporter: rhurlin at gwdg.de
Created attachment 207700
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207700&action=edit
New port astro/py-ephem 3.7.7.0
For more than 12 years now there is astro/pyephem in the ports. The recent
update of the sources changed the naming scheme from pyephem to ephem[1][2].
The version 3.7.7.0 in the ports is only a stub, which needs ephem as a
dependency[3].
Because several ports in the FreeBSD ports tree have astro/pyephem as a
dependency, the author Brandon Rhodes suggests to hold pyephem to direct to
ephem from there. Following this advice, I added astro/py-ephem as a dependency
in astro/pyephem and created a new port for ephem, astro/py-ephem. The naming
scheme follows other Python ports.
@wen: In the new port astro/py-ephem[4] I signed in as the maintainer. I would
be completely fine, if you instead want to be the maintainer, of course.
[1] https://rhodesmill.org/pyephem/
[2] https://pypi.org/project/ephem/
[3] Description section of PKG-INFO:l9-17
"This package is a stub
that contains no Python code,
but lists ``ephem`` as its install requirement
in case any old projects depend on this ``pyephem`` package name.
New projects are encouraged to directly require the main package,
which can be found at: https://pypi.org/project/ephem/ "
[4] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240735
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list