← Back to team overview

ubuntu-phone team mailing list archive

Re: Device-Specific configs in debs

 

On Tue, Jan 14, 2014 at 3:07 PM, Marc Deslauriers
<marc.deslauriers@xxxxxxxxxxxxx> wrote:
> On 14-01-14 05:46 PM, Alex Chiang wrote:
> >
> > Speaking with Steve Langasek yesterday, I got strong guidance that all
> > per-device configs really need to live in the customization tarball.
> >
> > And the customization tarball is only allowed to drop files into
> > /custom and $HOME.
>
> Please don't put stuff in $HOME, that's not appropriate for system stuff like
> udev rules and device configs.

Didn't mean to be confusing.

/custom and $HOME are the 2 options where the tarball is allowed to
put stuff. We choose the appropriate location depending on the use
case.

So I agree -- we do not put system stuff like udev rules into $HOME. :)

> >>> I propose that we try and tackle this before it becomes a problem.  Do we have a
> >>> plan for this already?
> >>>
> >>> If we don't have a plan quite yet, as a first step, I propose that we patch
> >>> powerd and apparmor to look in XDG_DATA_DIRS instead of just /usr/share/ for its
> >>> configs.  If we do this, we can drop any needed configs into a custom tarball
> >>> (which includes /custom/xdg/data, which is included in XDG_DATA_DIRS), and
> >>> therefore keep the rootfs as device-agnostic as possible.  Does this seem
> >>> reasonable?
>
> XDG_DATA_DIR is a weird variable to be using for system daemons, IMHO. Where
> does it get set? I'm ok with defining a location, but mixing unrelated stuff
> with xdg doesn't sound like a good idea to me.

There is a package (seeded, I think?) called ubuntu-touch-customization-hooks:

lp:ubuntu-touch-customization-hooks

In the package, there is an upstart job that sets this:

usr/share/upstart/sessions/custom-env.conf

I think we chose XDG simply because we had to choose something, and it
minimized the number of packages we'd potentially have to patch.

If there is a better location for system daemons, we're open to
suggestions. Keep in mind that all daemons would have to learn about
this new place to look for config files.


Follow ups

References