* Clint Adams <cl...@debian.org>, 2012-11-11, 23:19:
Yes, I'm aware of that. On the other hand: The current behavior seems
insane to me, unless there would be a good reason for by default
changing the umask to a less secure setting, but then that should be
documented.
I agree that the current run-parts behavior is indeed unfortunate.
I agree with your objection though. To avoid that kind of trouble, I'd
suggest a stepwise change:
* For the next release,
Next being wheezy or jessie? If the former, I'm afraid it's too late.
make run-parts issue a warning that it changes the umask, and that
this behavior is going to change in the future. Suppress the warning
if the user sets the umask with -u.
* For the following release, change run-parts to not tamper with the
umask anymore, and warn about the new situation, unless -u is given.
* Finally remove the warning.
Would that be of any use?
How about something that doesn't take more than a release cycle or
involve annoying warnings?
1) Identify packages that rely on the current behavior. File bugs.
2) Wait until wheezy is released.
3) Fix run-parts not to fiddle with umask by default. Add Debian.NEWS
explaining the situation.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121112142055.ga3...@jwilk.net
