Why does the RPM change permissions?
If there is a file permissions issue we should be fixing this in the
feature pack itself not the changing the permissions within the
provisioning system. There could be reasons why file permissions are the
way they are and we shouldn't make assumptions based on a file extension.
On Tue, Nov 28, 2017 at 6:37 AM, Romain Pelisse <belaran(a)redhat.com> wrote:
Hi,
As reported on JBEAP-12374[1], there is some discrepancies between the ZIP
file we provided for Widlfy/EAP and the RPM generate. Most of those
discrepancies - or the most relevant ones, are some fine tuning performed
on the (POSIX) privileges (things such as removing the write privilege for
member of the same group as the owner of the file).
I've looked into this and because those files are produced by our own
Maven plugin (as part of wildfly-build-tools), we can not simply modify the
assembly.xml. Which actually is probably for the best, as it would made the
assembly file quite cumbersome.
Anyhow, I've worked on a proposal[2] for the wildfly-build-tools, but when
I reported the problem on WFLY-9574[3], Brian suggested I started a
discussion here. So does anyone have a (strong) opinion about this issue
and/or how to resolve it ? :)
(For the record, I do think it is best to fix the privileges to follow
what the RPM does for us for now, but if you feel this issue should not be
addressed, and dev- the issue, I'm certainly not opposed to it either).
[1]
https://issues.jboss.org/browse/JBEAP-12374
[2]
https://github.com/wildfly/wildfly-build-tools/pull/40
[3]
https://issues.jboss.org/browse/WFLY-9574
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
James R. Perkins
JBoss by Red Hat