Re: Policy regarding /etc/profile.d
On Wed, Oct 15, 2014 at 11:20:21AM +0100, Simon McVittie wrote:
> On 15/10/14 00:17, Santiago Vila wrote:
> > Do we need a paragraph in policy saying explicitly "you should not use profile.d"?
>
> For some packages, like bash-completion and
> packagekit-command-not-found, the whole point of the binary package is
> to hook into shell startup and reconfigure the shell. What would you
> suggest that they should do instead?
We can make policy not to use profile.d, as a general rule, and then
require that people ask for exceptions (as we already do for
Pre-Depends) before introducing new files in /etc/profile.d.
In the examples you quoted, the permission would naturally be granted.
Reply to: