from gnome bug #669260
gmain: block child sources when blocking the parent
When blocking a source that has child sources, we need to consider the
children blocked as well. Otherwise they will still trigger repeatedly
in an inner loop started from the parent source's callback.
Fixes download dialog not rendered upon certain mimetypes on midori,
see https://bugs.launchpad.net/midori/+bug/780133
Note that some paths in gsettings have been deprecated
(/apps/, /desktop/ and /system/) which means that glib-compile-schemas
will now complain about them (just a warning).
It is up to the application itself to fix its schemas.
This module updates access and modification timestamps, creating
nonexistent files where necessary. In a fashion similar to touch(1).
from Abel Abraham Camarillo Ojeda
ok sthen merdely gsoares
zap groff while here.
0.64 Sat Dec 19, 2009, joern
Bugfixes:
- Accumulated group member errors were not reported to
the frontend.
- Use Perl's builtin command execution with a subshell
instead of forking.
The 1.0 serie hasn't seen an update for 5 years and this release
contains lots of fixes for new version desktops.
While here, remove the hook stuff; that is what aliases or ~/bin are for.
Params::Classify provides various type-testing functions. These are
intended for functions that, unlike most Perl code, care what type of
data they are operating on. For example, some functions wish to behave
differently depending on the type of their arguments (like overloaded
functions in C++).
MooseX::NonMoose allows for easily subclassing non-Moose classes with
Moose, taking care of the annoying details connected with doing this,
such as setting up proper inheritance from Moose::Object and installing
(and inlining, at make_immutable time) a constructor that makes sure
things like BUILD methods are called.
MooseX::MarkAsMethods allows one to easily mark certain functions as
Moose methods. This will allow other packages such as
namespace::autoclean to operate without blowing away your overloads.
After using MooseX::MarkAsMethods your overloads will be recognized by
Class::MOP as being methods, and class extension as well as composition
from roles with overloads will "just work".
Often you want to write a persistant daemon that has a pid file, and
responds appropriately to Signals. MooseX::Daemonize provides a set of
basic roles as an infrastructure to do that.
"require EXPR" only accepts "Class/Name.pm" style module names, not
"Class::Name". How frustrating! For that, we provide "load_class
'Class::Name'".
It's often useful to test whether a module can be loaded, instead of
throwing an error when it's not available. For that, we provide
"try_load_class 'Class::Name'".
Finally, sometimes we need to know whether a particular class has been
loaded. Asking %INC is an option, but that will miss inner packages and
any class for which the filename does not correspond to the package
name. For that, we provide "is_class_loaded 'Class::Name'".
Updated from 1.04 port in Andreas Voegele's repository.
''Currently, several ports that could be built with
"CONFIGURE_STYLE=modinst" are built with "CONFIGURE_ARGS += --skipdeps"
as they require a more recent version of Module::Install.''
