The Linux FS hierarchy [1] is pretty self-explanatory and standard. Unfortunately, many admins don't bother to actually read and understand what the heck is going on in their system. They have a tendency to follow poor documentation without verifying the quality of it. It's a bit disturbing that the archlinux wiki has that, but at the same time, it's edited by users.
We can't really police all documentation to ensure people use common sense. As much as it's not our place to police all documentation on the Internet, it's also not our place to protect users from every single silly thing they may consider doing. It's taking --no-preserve-root, and going a step further. Sure, this one could be a simple patch. It's a patch that isn't needed, though. I'm sorry to be blunt and perhaps a little rude, but there's only so much hand-holding and so on that should be provided. In my book, this one is well past the limit. I do have some ideas to help with this blind assumption that package territory is also user territory, but there's only so much that people will read. They obviously aren't bothering to read the top comment on the default nginx config. [1] http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard On Fri, Jan 16, 2015 at 3:40 PM, Arnout Engelen <arn...@bzzt.net> wrote: >> I've now verified that this is expected behavior. Regardless of whether we >> use /usr/share or /var/www, we have to expectation to retain user changes >> to >> index.html. We won't be making any change to preserve user changes to >> anything >> outside of /etc. > > > That is, of course, your call as maintainer. > > I do still feel we're not being responsible with our users' data here. Even > though > they shouldn't have been messing with /usr/share, a quick internet search > for > "/usr/share/nginx/html/index.html" reveals plenty of people doing just that. > > Arch's wiki even appears to encourage it: > > "It is assumed that you use the default location for documents > (/usr/share/nginx/html). If that is not the case, substitute your path > instead." - https://wiki.archlinux.org/index.php/Nginx#Configuring > > Would you consider a patch that backs the file up when it's changed? > Shouldn't be a big change: > we don't need to go to great lengths to support this situation, but just not > losing the file would > be nice :) > > > Yours, > > Arnout -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
