stefanozanella / fpm Goto Github PK

Currently, when you create a RPM using --rpm-use-file-permissions, --rpm-user and --rpm-group, the spec file that is built correctly contains a %defattr with the specified user and/or group; but, all the files contain also a %attr directive specifying not only the permissions, but also the ownership of the file, setting the ownership to that of the build system.

For example, consider you have a file like this:

-rw-r--r--  1 vagrant vagrant  2616 Feb 14 17:28 test.rb

that is packaged with the following fpm command:

fpm ... --rpm-use-file-permissions --rpm-user test --rpm-group test

This results in a spec file like this:

...
%defattr(-, test, test, -)
...
%attr(644, vagrant, vagrant) test.rb
...

thus overwriting the specified default. It would be more useful, instead, if the following output is produced:

...
%defattr(-, test, test, -)
...
%attr(644, -, -) test.rb
...

This would allow to actually mix the two/three options, as the installed file will keep the original permissions, while using the custom user/group specified at wrapping time.

NOTE: The issue can be solved by modifying FPM::Package::RPM#rpm_file_entry