Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
issue 245 (RPM's with non-root owners doesn't set ownership of directori... #260
I've added a --directories argument to FPM which causes the values to be added as %dir entries under the file list, so they take the --rpm-user and --rpm-group as owners and get removed when the RPM gets removed. As you can see, it works just like --config-files.
What do you think?
Thanks and Regards,
…ories). Add a --directories argument, which in a similar way to --config-files allows directories to be tagged as directories, meaning they are owned by the RPM. This means they get the --rpm-user and --rpm-group as their owners, and they are removed with the RPM.
Hi, this sounds good, as it solves our problem of ensuring that our directories are getting created with the right users/groups- thanks!
Could it be taken further? It would be FANTASTICALLY-USEFUL if there were a way of defining per file/directory permissions within the resultant RPM (which is possible when using a spec file). I don't know what would be the best way of assigning the permissions?