Date: Sun, 23 Jul 2017 09:06:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219687] [NEW PORT] net/google-compute-engine: User daemon for Google Compute Engine Message-ID: <bug-219687-13-J475DGwjW1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219687-13@https.bugs.freebsd.org/bugzilla/> References: <bug-219687-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219687 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koobs@FreeBSD.org |freebsd-ports-bugs@FreeBSD. | |org --- Comment #17 from Kubilay Kocak <koobs@FreeBSD.org> --- - Patches should be commented/referenced (upstream issues/commits) where possible - Port should use python framework components (use=3Dpython, use_python, et= c) 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 call= ed 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 (al= beit 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 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219687-13-J475DGwjW1>