1 |
For the past several weeks I've found it impossible to emerge sage from the |
2 |
sage-on-gentoo overlay because the ebuild for sage-5.2 (~amd64) and |
3 |
sage-5.3_beta2 (masked) requires ~dev-python/networkx-1.6. However |
4 |
networkx-1.6 is not in portage any longer; networkx-1.2 is in the overlay and |
5 |
networkx-1.7 is in portage. |
6 |
|
7 |
sage-5.1 had a networkx-1.6 specific patch but I don't see any patches in |
8 |
sage-5.2 that are networkx specific. |
9 |
|
10 |
Should I copy the sage ebuild into my local overlay and change the dependency |
11 |
to networkx-1.7? I'd be glad to be warned if any one knows of any problem I |
12 |
would encounter before I invest the time to try emerging sage to use the newer |
13 |
version of networkx. |
14 |
|
15 |
I also was wondering why dev-python/networkx is required; I thought that |
16 |
networkx was integrated into sage? |