blob: b50a9429519e0e054d29e1e171b52811ed7821ed (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
Registry Change Hooks
----------------------
This document proposes a mechnism to register on registry updates.
Last edited: 2009-11-09 Stefan Kost
Current Behaviour
-----------------
When new plugins are installed or some are removed, the next application that
runs rebuiilds the registry. Any application that runs later on won't know about
it.
Problem
-------
Some usecases need to cache gstreamer capabilities. They need to know when the
cache needs to be rebuilt. We could either export the registry mtime as api or
do the following.
Proposal
--------
We add a ~/.gstreamer-0.10/registry-hooks directory. Applications can install
scripts there. When the registry is rebuild, those scripts are run async in no
specific order. There is no feedback channel (return values, stdout/err).
Examples
---------
gst-inspector
-------------
it would install a script that simply deletes its cachefile.
gupnp
-----
it would install a script that runs gst-inspect-0.10 --print-plugin-auto-install-info
and post process it.
totem,banshee,rythmbox
-----------------------
they could tune the "MimeType=" lists in their desktop files
Open Items
----------
Should we have a gst-registry-hook script with --install/--remove/--list actions
to manage hooks?
|
