[Bug 219687] [NEW PORT] net/google-compute-engine: User daemon for Google Compute Engine

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Jul 23 09:06:55 UTC 2017


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

Kubilay Kocak <koobs at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|koobs at FreeBSD.org           |freebsd-ports-bugs at FreeBSD.
                   |                            |org

--- Comment #17 from Kubilay Kocak <koobs at FreeBSD.org> ---
- Patches should be commented/referenced (upstream issues/commits) where
possible
- Port should use python framework components (use=python, use_python, etc)

Also, rationale/more information on the following would be useful:

- A separate google-config port with no dependency registered on it. Could this
(google-compute-engine) port install the configs itself instead?

- References to rsyslog / udev, without associated dependencies on rsyslog or
libudev (if needed). If these configs are being modified to work with base
freebsd functionality and installed in base directories, are they just called
rsyslog/udev  to stick with upstream naming of modules?

- Installation and integration of files into base directories. The need for
this (installing into base) should be actual, compelling and well tested, or
alternatives implemented.

Given the above complexity I wont be able to review it in the detail that it
appears to need at the moment. If the port is modified to be a standard (albeit
even substantially modified) python package, please feel free to re-assign to
me.

I'm happy to continue to review python specific issues/questions on request

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


More information about the freebsd-python mailing list