Date: Wed, 17 Oct 2018 13:21:57 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 232330] [NEW PORT] www/chrome-gnome-shell: GNOME Shell integration for Chrome Message-ID: <bug-232330-6497-ZFaLl1jQyx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-232330-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-232330-6497@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=3D232330 --- Comment #3 from Ting-Wei Lan <lantw44@gmail.com> --- Comment on attachment 198236 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D198236 chrome-gnome-shell.diff >+GH_ACCOUNT=3D Gnome >+USE_GNOME=3D pygobject3 >+USE_GITHUB=3D yes GNOME uses its own GitLab instance (gitlab.gnome.org) instead of GitHub, so= I think it is usually discouraged to use USE_GITHUB in GNOME ports because us= ers may wrongly assume the project is maintained on GitHub and file issues or p= ull requests there, which are likely to be ignored for months or even years. Th= ere are USE_GITLAB and GL_SITE which you can use, but in this case there is a better option. Since you are packaging a stable release, you can simply use= the release tarball on GNOME download site: https://download.gnome.org/sources/chrome-gnome-shell/. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232330-6497-ZFaLl1jQyx>