Hi Nelson,

Le dimanche 25 décembre 2011, à 19:04 +0000, Nelson Marques a écrit :
> Hi all,
> 
> MATE Desktop uses a fork of gconf called mateconf. This stuff uses the
> traditional schemas files and there's a few things I would like to ask
> from someone more proeficient in this ways to accomplish for
> openSUSE...
> 
> With gconf as far as I can tell, the schema files were created in
> /etc/gconf/foobar.schema and a macro we invocked would then move them
> to /usr/share/GConf/ and merge them up.
> 
> mateconf is pretty much the same... files are created in
> /etc/mateconf/schemas and later need to be moved to
> /usr/share/mateconf. Debian does it this way:
> 
> 
> mkdir -p debian/mate-terminal/usr/share/mateconf/schemas
> mateconf-merge-schema
> "debian/mate-terminal/usr/share/mateconf/schemas/mate-terminal.schemas"
> \
>                                      --domain mate-terminal
> debian/mate-terminal/etc/mateconf/schemas/*.schemas
> rm -rf debian/mate-terminal/etc/mateconf/schemas/
> 
> 
> What I would like to achieve was to make an rpm macro like the one we
> use for gconf schemas so we can handle this situations more
> efficiently on openSUSE, but I would also like to donate this macro to
> the 'mate-common' package, which is a set of tools used to build mate
> (it is BuildRequired in all packages, except for itself. It contains
> m4 macros alongside with other tools).
> 
> 
> Anyone with power and know-how that can help me accomplish this ?

It's unclear to me: is mate-common based on some upstream tarball, or
does it just contain some openSUSE specific bits?

If you're looking for a downstream-only solution: any reason to not do
it exactly the way it's done for gconf?

If you're looking for an upstreamable solution: I'd think the directory
where to put schema files could be a variable in the mateconf pkg-config
file, and then all modules would use that variable.

Cheers,

Vincent

-- 
Les gens heureux ne sont pas pressés.
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to