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 781012 - Pick up the unstable manifest when possible
Pick up the unstable manifest when possible
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: general
3.23.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks: 781010
 
 
Reported: 2017-04-07 08:24 UTC by Carlos Soriano
Modified: 2018-01-11 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Carlos Soriano 2017-04-07 08:24:06 UTC 
Applications in GNOME now deliver different manifests for different versions. GNOME Builder picks up the first that finds (I think), but we would probably one to take the unstable one, since building another version is something that probably only the maintainer would do for testing reasons.

For that, maybe we can add a "gotcha" and always pick up the manifest with *unstable* in the file name?

This is good for the newcomers experience.
Comment 1 Matthew Leeds 2017-04-07 19:00:41 UTC 
Builder does find both, but I guess you're saying the unstable one should be selected by default, unless the user has previously selected another. I wonder where that preference would be persisted to.
Comment 2 Christian Hergert 2017-04-07 20:22:52 UTC 
We can add a relocatable gsettings schema that is org.gnome.builder.project with a path like /org/gnome/builder/projects/$project_id which contains the id of the default configuration.
Comment 3 Carlos Soriano 2017-04-07 21:28:11 UTC 
(In reply to Matthew Leeds from comment #1)
> Builder does find both, but I guess you're saying the unstable one should be
> selected by default, unless the user has previously selected another. I
> wonder where that preference would be persisted to.

Yeah. Either that, or maybe we should educate the developer. Thing is Builder starts the background download already with the first one :(
Comment 4 GNOME Infrastructure Team 2018-01-11 10:24:57 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-builder/issues/212.