[MacPorts] #46696: py-python-poppler-qt4: rename to py-poppler-qt4 and use PyPI
MacPorts
noreply at macports.org
Thu Jan 29 16:05:14 PST 2015
#46696: py-python-poppler-qt4: rename to py-poppler-qt4 and use PyPI
-------------------------------------------------+-------------------------
Reporter: davide.liessi@… | Owner: petr@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: haspatch
Port: py-python-poppler-qt4 py-poppler- | maintainer
qt4 frescobaldi |
-------------------------------------------------+-------------------------
Comment (by davide.liessi@…):
To be more precise:
Replying to [comment:5 petr@…]:
> In future, please avoid submitting combined files and provide unified
diffs.
I understand that (according to
[https://guide.macports.org/#development.patches.portfile the guide]) I
should have submitted diff files for each one of py-python-poppler-qt4 and
py-poppler-qt4, but...
> The Portfile for py-poppler-qt4 is not really new, it has a history we
want to preserve
... py-poppler-qt4 is a new file, although it has similar content to the
old py-python-poppler-qt4; on the other hand the new py-python-poppler-qt4
is completely different from the old one, so I thought it was clearer to
read the new portfile instead of a meaningless diff.
How should I have prepared a "history-preserving" diff?
> and we are supposed to commit non-semantic format changes as separated
changesets.
I don't think I understand this part.
--
Ticket URL: <https://trac.macports.org/ticket/46696#comment:7>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list