Re: [sigc] Move to GitHub?
- From: Murray Cumming <murrayc murrayc com>
- To: Kjell Ahlstedt <kjellahlstedt gmail com>
- Cc: libsigc-list <libsigc-list gnome org>
- Subject: Re: [sigc] Move to GitHub?
- Date: Tue, 27 Feb 2018 20:46:30 +0100
On Mon, 2018-02-26 at 13:50 +0100, Kjell Ahlstedt wrote:
Have you seen the following comment in jhbuild's moduleset file?
https://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-suites-cor
e-deps-3.28.modules
<!-- WARNING: github.com is only allowed here under one of two
conditions:
(a) The module has tarball releases elsewhere (e.g. GNOME
infrastructure)
(b) The module is always built from tarball, never from git
If (a) does not apply then you must build from tarball (github-tar)
if adding
a GitHub module here. Otherwise our release infrastructure will
fail to handle
the module and we will just change it to use a tarball anyway.
-->
I don't know if it matters, when you decide where to store libsigc++
in the future.
Thanks. I'm not greatly troubled that that, though it is a bit odd.
Either continuing to release tarballs on gnome servers, or just using a
tarball in jhbuild, are not great disadvantage.
--
Murray Cumming
murrayc murrayc com
www.murrayc.com
[
Date Prev][Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]