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 713309 - GSettings not removed on clean
GSettings not removed on clean
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: build
unspecified
Other All
: Normal normal
: 0.13.0
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 777044
Blocks:
 
 
Reported: 2012-04-24 01:56 UTC by Eric Gregory
Modified: 2018-06-26 04:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:20:06 UTC


---- Reported by eric@yorba.org 2012-04-23 18:56:00 -0700 ----

Original Redmine bug id: 5110
Original URL: http://redmine.yorba.org/issues/5110
Searchable id: yorba-bug-5110
Original author: Eric Gregory
Original description:

When we switched to CMake (see #4982) I had to create a GSettings module from
scratch. Unfortunately I wasn't able to figure out how to remove the files it
creates with make clean; ideally the entire gsettings folder should be
removed, along with the schema file(s) and compiled GSettings file.



---- Additional Comments From geary-maint@gnome.bugs 2013-01-15 18:11:00 -0800 ----

### History

####

#1

Updated by Jim Nelson 10 months ago

  * **Category** set to _build_



--- Bug imported by chaz@yorba.org 2013-11-21 20:20 UTC  ---

This bug was previously known as _bug_ 5110 at http://redmine.yorba.org/show_bug.cgi?id=5110

Unknown version " in product geary. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Federico Bruni 2017-12-04 06:43:29 UTC
I've just made a test and after running `make clean` I can see that these files are still there:

$ ls build/gsettings/
gschemas.compiled  org.gnome.Geary.gschema.xml
Comment 2 Michael Gratton 2017-12-04 06:48:45 UTC
Lets fix this after moving to meson. Adding a dep on Bug 777044.
Comment 3 Michael Gratton 2018-06-13 12:51:04 UTC
The Meson build now generates the file in the build dir, so resolving as fixed.