summaryrefslogtreecommitdiff
path: root/plugins/housekeeping/msd-housekeeping-manager.c
AgeCommit message (Collapse)AuthorFilesLines
2019-08-20msd-housekeeping-manager: avoid 'g_type_class_add_private'Pablo Barciela1-5/+2
2016-06-25housekeeping: replace buggy thumb-cleaning code with correct onemonsta1-55/+14
also remove defines for default max age and size - we already have the defaults set in schema, makes no sense to duplicate them here. early check for -1 value (means "do not clean thumbs") is ported from: https://git.gnome.org/browse/gnome-settings-daemon/commit?id=12f2121929f048c5cc07cd9c90570310a169b29e
2014-12-16Revert "Add back Glib 2.32 support"infirit1-16/+0
This reverts commit 602945c084d45bd3858e564e03a70a2a361a5756.
2014-12-16Add back Glib 2.32 supportinfirit1-0/+16
2014-05-18Drop support for glib < 2.36infirit1-15/+0
2013-09-26housekeeping: Support new thumbnails path for newer glib versionsStefano Karapetsas1-0/+15
Closes #51 https://github.com/mate-desktop/mate-settings-daemon/issues/51
2012-12-15[housekeeping] Use g_settings_get_mapped, fix paranoid cleanup on shutdownJasmine Hassan1-44/+62
1. Use g_settings_get_mapped instead of our own hack get_gsettings_int_with_default. 2. Don't force hard-coded default when value is 0, as that's used to allow paranoid scanning on shutdown. 3. Only unref the settings object at the end of _stop routine, not before do_cleanup is potentially called, since purge_thumbnail_cache uses the settings. This was also causing asserts when killing msd, as described in (now closed) #23. These are regressions introduced by the gsettings port of the plugin -- 03478b4d
2012-10-12fix incorrect FSF addressraveit651-1/+1
2012-10-01migrate to gsettingsmate-settings-daemon-1.5.0Stefano Karapetsas1-4/+2
2012-09-03port msd-housekeeping-manager.c to gsettingsStefano Karapetsas1-61/+23
2012-02-21gsd to msd complete rename patch by NiceandGently; file rename commithaxar1-0/+389