Created attachment 173352 [details]
- moved to github
- depend on newer sqlalchemy10
testbuilds are fine, portlint is fine.
Created attachment 173353 [details]
updated pkg-descr with new WWW
which is not very specific.
This is one of those annoying times where the product name (pycogent) and the python package name (cogent) differ.
I was going to suggest a rename, until I realised the package name was the only thing difference (compared to their domain, titles and messaging).
While in most cases I suggest that upstreams don't prefix their python package names with 'py' in PyPI, in this case it would be 'really' nice if we could ask upstream to rename theirs to pycongent, so the package name matches the product name.
@Kurt, since PyCogent doesn't yet support Python 3, USES=python should be USES=python:-2.7 to be explicit and accurate
At some point (if not now) when a Python 2 and 3 compatible version is released, this port will need a PYTHON_PKGNAMEPREFIX to support concurrent installs, so if you want to do that now feel free.
A commit references this bug:
Date: Mon Aug 8 11:21:04 UTC 2016
New revision: 419818
- Update to 1.9 
- Moved to github 
- Depend on newer sqlalchemy10 
- Update pkg-descr and WWW 
- Limit python to -2.7 
- Reset maintainer to python@ for better maintain
Submitted by: pi@ , koobs@