After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 663813 - Switch to main 3.4 moduleset
Switch to main 3.4 moduleset
Status: RESOLVED DUPLICATE of bug 668440
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-11-10 22:20 UTC by Colin Walters
Modified: 2012-02-08 21:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
build-setup.sh: Allow specifying INSTALL_PACKAGES=no ./gnome-shell-build-setup.sh (1.12 KB, patch)
2011-11-10 22:20 UTC, Colin Walters
rejected Details | Review
build: Switch to main 3.4 moduleset (17.12 KB, patch)
2011-11-10 22:20 UTC, Colin Walters
none Details | Review

Description Colin Walters 2011-11-10 22:20:10 UTC
The gnome-shell one has bitrotted significantly.
Comment 1 Colin Walters 2011-11-10 22:20:12 UTC
Created attachment 201193 [details] [review]
build-setup.sh: Allow specifying INSTALL_PACKAGES=no ./gnome-shell-build-setup.sh

This allows one to rerun other parts of the script without suffering
through the whole packagekit etc. mess.
Comment 2 Colin Walters 2011-11-10 22:20:16 UTC
Created attachment 201194 [details] [review]
build: Switch to main 3.4 moduleset

The separate moduleset is even less well maintained than the main
jhbuild one.
Comment 3 Owen Taylor 2012-02-08 20:59:16 UTC
Review of attachment 201193 [details] [review]:

The general approach of the script is that it checks for all the deps before running PackageKit or equivalent, so it should be (reasonably) fast and convenient to just run it normally. It is for me on Fedora, anyways.

(This patch makes INSTALL_PACKAGES=yes mean "don't install packages...")
Comment 4 Owen Taylor 2012-02-08 21:02:33 UTC
Duplicating on bug 668440 which is basically the same thing but has a little more up-to-date patch that I've been working from.

*** This bug has been marked as a duplicate of bug 668440 ***