[
http://jira.codehaus.org/browse/MOJO-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160935#action_160935
]
Brett Okken commented on MOJO-1058:
-----------------------------------
Is this indirectly fixed by MOJO-931 (at least partially)?
In the case you have given, I believe the .spec would have:
%attr(644,root,root) /path/foo/bar.txt
A <dirmode> could potentially work, however having an second mapping just for
the directory to specify username, groupname, and filemode for the directory
explicitly does not seem terribly onerous.
> <filemode> is used for directories
> ----------------------------------
>
> Key: MOJO-1058
> URL: http://jira.codehaus.org/browse/MOJO-1058
> Project: Mojo
> Issue Type: Bug
> Components: rpm
> Reporter: Jürgen Hermann
>
> A mapping like this:
> <mapping>
> <directory>/path/foo</directory>
> <username>root</username>
> <groupname>root</groupname>
> <filemode>644</filemode>
> <sources>
> <source>bar.txt</source>
> </sources>
> </mapping>
> leads to this in the generated .spec:
> %attr(644,root,root) /path/foo
> Problem here is that the "foo" directory gets the filemode too, as do any
> subdirectories, resulting in unbrowsable directory structures.
> The *workaround* for the root dir is to repeat the mapping w/o a source
> section and a filemode of 755 (which is tedious at best).
> A proper solution would be to use %attr(-,u,g) and set the permissions
> dynamically while copying into the target (build-stage) directory, which
> would also work for any subdirs. Also, there should be a <dirmode> in
> addition to <filemode>.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
