Niels Thykier schrob: > Having debhelper support/do this will have no influence on whether init > or login systems will need to support it in the first place AFAICT.
True.
> The use case in debhelper is to setup an empty directory and point an
> ENV variable at it to ensure we get a defined result *if* a tool uses
> that ENV variable (namely, the tool gets a writeable empty directory for
> the duration of the build).
Yes. But if you don't set XDG_RUNTIME_DIR, you also get a (tool-)defined
result¹. Unless the tool contains a bug to not handle that case properly.
So I think the only thing you're doing here is papering over possible
bugs.
> Note that debhelper's usage do *not* follow the spec to the letter -
> unless we define the build start to as a "login" and d/rules clean as a
> "logout".
That's even more of a reason to not do that then.
(You might even break things by hiding contents of the XDG_RUNTIME_DIR
of the user invoking debhelper. That used to be a problem a longish time
ago, no idea how it is nowadays.)
cheers,
Jan
¹most likely involving $TMPDIR, so you should achieve the same effect by
setting that.
signature.asc
Description: PGP signature
