-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debian postinst chowns install path #223
Comments
Nope. Read on the docs for exact default chown/chmod properties. This is issue has been discussed in #170 , #174 , #178 and #210 :) How mappings are handledAs this is still a documentation issue, I will explain the debian mappings here in a bit more detail and put them into the docs, when I got time. You define a mapping packageMapping(
file1 -> "/usr/share/file1",
file2 -> "/usr/share/file2"
) withUser "youruser" withGroup "yourgroup" With this definition two entries are generated in the chown youruser:yourgroup /usr/share/file1
chown youruser:yourgroup /usr/share/file2 If you want to own a complete directory by a specific user, user one of the Each directory/file in the mapping will then get a |
The behavior I'm seeing is at odds with the documentation. The documentation says that |
You are right, I'll fix this today |
Awesome, thanks! |
postinst-chown
includes the lineYet all files underneath this path are owned by root. Shouldn't it be one way or the other? (All root or all daemon user?)
The text was updated successfully, but these errors were encountered: