Dear list,
Touching files under $HOME in a postrm script is obviously a bad idea. However, a colluegue insists in trying to make me do this.
Just to resolve this issue: is the the limitations on what files which
can be touched by a packaging script documented somewhere?
I have been skimming through the Policy Manual, but no luck. Did I miss something? Is it somewhere else? Or is it just an undocumented "good judgment" thing?
Any clue, out there?
Touching files under $HOME in a postrm script is obviously a bad idea. However, a colluegue insists in trying to make me do this.Under which of the home dirs? Normally it just doesn't make sense to find
Just to resolve this issue: is the the limitations on what files whichI think it's the latter, together with what I said above.
can be touched by a packaging script documented somewhere?
I have been skimming through the Policy Manual, but no luck. Did I miss something? Is it somewhere else? Or is it just an undocumented "good judgment" thing?
On Tue, May 04, 2021 at 04:46:42AM +0200, Alec Leamas wrote:
Touching files under $HOME in a postrm script is obviously a bad idea.
However, a colluegue insists in trying to make me do this.
Under which of the home dirs? Normally it just doesn't make sense to find
all real users and then find and access their homedirs, especially taking into account various complex setups.
Just to resolve this issue: is the the limitations on what files which
can be touched by a packaging script documented somewhere?
I have been skimming through the Policy Manual, but no luck. Did I miss
something? Is it somewhere else? Or is it just an undocumented "good
judgment" thing?
I think it's the latter, together with what I said above.
Describe the original goal, tell what you want to achieve.
Why the need for touching files under $HOME.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (2 / 14) |
Uptime: | 87:24:22 |
Calls: | 6,496 |
Calls today: | 7 |
Files: | 12,100 |
Messages: | 5,277,153 |