https://bugzilla.redhat.com/show_bug.cgi?id=1764368
Petr Menšík <pemensik(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(robert.fuehricht@
| |jku.at)
--- Comment #5 from Petr Menšík <pemensik(a)redhat.com> ---
(In reply to Robert Führicht from comment #2)
Michael, thanks for your review - I fixed the things you mentioned
except
this one:
> It really must not store any packaged files in user home directory, and that it
includes /root.
I'm unsure about how to make duc behave in the way I want then - see the
remark about proposed usage.
The possibilities I came up with are these:
- Provide a system-wide ducrc: Doesn't work, as this would need
user-specific default overrides.
- Provide a rc file for root: Against packaging policy.
- Set DUC_DATABASE=/var/cache/duc for root (and only root):
- /etc/environment is out, as it concerns all users.
- Dotfiles for root are out, packaging policy again.
- /etc/profile.d/ drop-in works, but is shell-specific.
So should I drop this and consider this not the packager's job, or is there
something I'm missing?
Why don't you set environmnent (In reply to Robert Führicht from comment #2)
Michael, thanks for your review - I fixed the things you mentioned
except
this one:
> It really must not store any packaged files in user home directory, and that it
includes /root.
I'm unsure about how to make duc behave in the way I want then - see the
remark about proposed usage.
The possibilities I came up with are these:
- Provide a system-wide ducrc: Doesn't work, as this would need
user-specific default overrides.
- Provide a rc file for root: Against packaging policy.
- Set DUC_DATABASE=/var/cache/duc for root (and only root):
- /etc/environment is out, as it concerns all users.
- Dotfiles for root are out, packaging policy again.
- /etc/profile.d/ drop-in works, but is shell-specific.
So should I drop this and consider this not the packager's job, or is there
something I'm missing?
Maybe set DUC_DATABASE from systemd unit. I doubt there is reason why root
should have different behaviour from other users. Instead, prepare systemd
service for running the service on system level. And allow users to run own
instances as user level. I have suggested few ways. Is any of them suitable to
you?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component