py-poppler variants vs separate ports

[Davide Liessi]

2013/8/15 Sterling Smith <smithsp at fusion.gat.com>:
> Also, we should try to avoid collisions in filespace; here are the contents of my py-poppler (sub)port
> {{{
> $ port contents py-poppler
> Port py-poppler contains:
>   /opt/local/share/doc/py-poppler/README
> $ port contents py27-poppler
> Port py27-poppler contains:
>   /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/poppler.la
>   /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/poppler.so
> }}}

There shouldn't be any collisions:

$ port contents py27-python-poppler-qt4
Port py27-python-poppler-qt4 contains:
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/popplerqt4.so
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/python_poppler_qt4-0.16.3-py2.7.egg-info/PKG-INFO
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/python_poppler_qt4-0.16.3-py2.7.egg-info/SOURCES.txt
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/python_poppler_qt4-0.16.3-py2.7.egg-info/dependency_links.txt
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/python_poppler_qt4-0.16.3-py2.7.egg-info/top_level.txt

Best wishes.
Davide Liessi