Commit Graph

10 Commits

Author SHA1 Message Date
Sebastian Keller
1c7eb13caf git: Always use libgnome-volume-control submodule from GNOME group
Otherwise CI will fail for anyone who does not have a fork of it in
their personal projects.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2403>
2022-08-04 18:31:16 +02:00
Florian Müllner
c865d1b414 git: Use relative URL for external submodule
Gitlab recommends using relative URLs for submodules on the same
server[0], so do that.

[0] https://docs.gitlab.com/ee/ci/git_submodules.html

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2371>
2022-08-01 13:00:10 +02:00
Andre Klapper
fb39cc5952 submodules: Replace non-functional git.gnome.org URL by GNOME Gitlab URL
Fixes 
2018-09-25 08:41:30 +02:00
Florian Müllner
3fe45e29e4 theme: Replace gnome-shell-sass submodule with subtree
As the style has grown bigger and more complex, generating the different
variants from a common source has been a good decision. However given how
intertwined the theme is with gnome-shell itself, relying on a submodule
has proven to be quite painful. And as things stand right now, it is going
to get worse:

 - using either pre-generated CSS or generating it at build time is
   odd, and violates meson's strict separation between source- and
   build directories; we are therefore considering dropping the CSS
   and depending on sassc to always generate it at build time

 - with the migration to gitlab, our workflow shifts decisively towards
   branches; however there is no support in either git or gitlab for
   handling two brances of separate repositories consecutively, which
   gets particularly awkward for branches in a private namespace

With those pain points in mind, we will adjust our setup as follows:

 - remove the submodule from gnome-shell and instead import the
   sass as subtree

 - after that, the sass sources can be changed like any other files
   in the repository, and regular contributors can forget that there
   was ever anything special about them

 - whenever we want to update the classic style, we can push the subtree
   changes and bump gnome-shell-extension's sass submodule

In other words: Updating the classic styling will become slightly more
painful, but not much and only for me; in return, everyone else can
stop fiddling with submodules (and buy me a beer).
2018-02-09 21:45:09 +00:00
Mathieu Bridon
619a69d53c Use HTTPS URLs for the submodules
The git protocol is usually blocked in conference/hotel networks, and it
is vulnerable to MITM attacks.
2017-08-02 16:32:16 +02:00
Florian Müllner
7f4e914b00 build: Move gvc submodule to /subprojects/gvc
When using the meson build system, gvc will be built as a subproject.
As meson restricts submodules to a subprojects/ directory in the
source tree root, move the submodule there.

https://bugzilla.gnome.org/show_bug.cgi?id=783229
2017-07-19 21:24:08 +02:00
Colin Walters
4c91db4661 gitmodules: Fix URL for previous commit 2015-02-20 17:08:42 -05:00
Javier Jardón
09c38fda51 .gitmodules: Use git protocol instead https 2015-02-20 21:57:07 +00:00
Carlos Soriano
e317bfdab7 theme: Use gnome-shell-sass as a submodule
The sass sources now live in a project in GNOME, so they can
be used in multiple projects like gnome-shell-extensions.
Because of that, add gnome-shell-sass as a submodule of gnome-shell
and remove the sass sources from the theme directory.
2015-02-20 17:15:29 +01:00
Giovanni Campagna
3af9f636af Use libgnome-volume-control from a submodule
To be shared with gnome-control-center and gnome-settings-daemon
2012-12-08 15:53:46 +01:00