[MacPorts] #46696: py-python-poppler-qt4: rename to py-poppler-qt4 and use PyPI
MacPorts
noreply at macports.org
Tue Jan 27 15:31:23 PST 2015
#46696: py-python-poppler-qt4: rename to py-poppler-qt4 and use PyPI
-------------------------+-------------------------------------------------
Reporter: | Owner: macports-tickets@…
davide.liessi@… | Status: new
Type: enhancement | Milestone:
Priority: Normal | Version:
Component: ports | Port: py-python-poppler-qt4 py-poppler-
Keywords: haspatch | qt4 frescobaldi
maintainer |
-------------------------+-------------------------------------------------
I decided to rename `py-python-poppler-qt4` and to use PyPI as source
instead of GitHub (see the thread starting with
[https://lists.macosforge.org/pipermail/macports-
dev/2015-January/029522.html this message]).[[BR]]
I had to remove the entry about `py-python-poppler-qt4` from `py-
graveyard` because MacPorts cannot handle "replaced_by chains" (see the
thread starting with [https://lists.macosforge.org/pipermail/macports-
dev/2015-January/029525.html this message]).
The changes are meant to be applied all at once:
* the Portfile for the **new** port `py-poppler-qt4` is `Portfile-py-
poppler-qt4`;
* the `py-python-poppler-qt4` Portfile must be **replaced** by `Portfile-
py-python-poppler-qt4`;
* the `frescobaldi` Portfile must be **patched** with `Portfile-
frescobaldi.diff`;
* the `py-graveyard` Portfile must be **patched** with `Portfile-py-
graveyard.diff`.
--
Ticket URL: <https://trac.macports.org/ticket/46696>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list