Bug#723948: libatk-bridge-2.0-0-udeb: uninstallable; depends on missing libatspi2.0-0 (>= 2.9.4)
On Sat, 21 Sep 2013 at 17:43:13 +0200, Samuel Thibault wrote:
> Ah, damn, sure. Will do. This will however also need a udeb for
> libdbus, thus cloning for dbus too.
Sorry for the delay, I didn't see this until just now.
Is there any general documentation on creating udebs/how they should
differ from full-fat debs, or should I base some guesses on another
udeb-enabled package, like glib2.0 or something?
How space-constrained are we here? Should I be compiling the udeb "flavour"
with -Os, disabling API sanity checks (that aren't triggered by correct code)
to save a bit of space, or similar hacks?
The obvious core feature is "enough of the libdbus library that dynamic
linking succeeds", but presumably AT-SPI isn't just linking to libdbus
for fun, and needs some subset of its functionality.
What functionality do you need the libdbus udeb(s) to have? Specifically:
Does AT-SPI run its own DBusServer in-process (in which case it might
only need the library), or does it execute the dbus-daemon binary?
Does AT-SPI need the well-known D-Bus system bus to be running from
its init script, or can we leave out that bit?
If AT-SPI does need the system bus, I assume we don't need SELinux support,
or systemd-as-pid-1 enhancements?
dbus-daemon and parts of libdbus require that a unique "machine UUID" (32
lower-case hex digits + "\n", no punctuation) has been generated and stored
in either /etc/machine-id (systemd-compatible location) or
/var/lib/dbus/machine-id (old location). Should dbus-udeb arrange for that
to happen in its postinst, or would you prefer d-i to set up
Are udebs expected to be robust across a reboot? I assume "no"?
(If they're not, then we can create machine-id in the postinst, but not
bother to check/re-create it in an init script.)
Do you want the dbus-launch utility to start/discover a session bus
automatically (packaged as dbus-x11, 28K, adds libX11) or can we omit that?
Do you want the dbus-send utility for sending messages from the
command line (20K) or can we omit that?
Do you want the dbus-monitor utility for monitoring D-Bus traffic? (16K)