[Bug 201280] devel/gaphor: Missing etk.docking dependency

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201280

Kubilay Kocak <koobs at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |koobs at FreeBSD.org,
                   |                            |python at FreeBSD.org
           Keywords|                            |needs-patch, needs-qa
              Flags|                            |maintainer-feedback-
            Summary|devel/gaphor: Port          |devel/gaphor: Missing
                   |prerequisites defect?       |etk.docking dependency

--- Comment #1 from Kubilay Kocak <koobs at FreeBSD.org> ---
It appears this port manually (attempts to) install the etk.docking dependency
[1]

Having said that there are a few issues with the state of this port in general. 

For example it appears to BUILD_DEPENDS on py-nose (a unit testing framework)
which is very likely bogus. 

This itself however, is unlikely to cause the issue reported here, but is a
reflection of the probable quality and robustness of the port in general.

This port is currently unmaintained, and as such I would recommend that you
attempt to isolate the root cause of why the port doesn't correctly install
etk.docking as it attempts to do.

Additionally, using easy_install to install Python packages into the system
site-packages path is completely unsupported (and not recommended) as it
bypasses ports/package management systems.

If you would like assistance isolating the root cause of this, you are welcome
to join #freebsd-python on the freenode IRC network.

You are correct however that a port requiring additional python dependencies,
should either do so itself, or as recommended, with ports of those python
packages.

[1]
https://svnweb.freebsd.org/ports/head/devel/gaphor/Makefile?revision=371280&view=markup#l8

-- 
You are receiving this mail because:
You are on the CC list for the bug.