Hi
Sorry for the late answer, been very busy lately.
sverhagen wrote:
Hi, I'm using the following configuration for creating a Debian assembly with
the UNIX plugin:
(unix-maven-plugin:package-deb)
<copyDirectory>
<fileAttributes>
<user>root</user>
<group>root</group>
<mode>0755</mode>
</fileAttributes>
<from>${project.build.directory}/${finalName}</from>
<includes>
<include>**.sh</include>
</includes>
<to>/opt/pkg-${artifactId}</to>
</copyDirectory>
The .sh files are nicely there, though in rw-r--r-- permissions (both in the
build directory and in the .deb package). Am I doing something wrong, or is
this a bug? I tried looking in the code (a lot!), but I can't figure out
where these permissions are supposed to be applied while writing these files
to the build directory.
That's a 'feature' of how the dpkg tools work. The plan is to implement
the dpkg support in pure Java giving us the ability to control it as we
want.
What people do today that create debs is to run a postinstall script to
adjust the permissions.
As a matter of fact, a quick tests indicates that I'm suffering the same
problem when doing package-rpm.
That should work as the permissions are controlled from the spec file.
I used today's trunk/HEAD version (r10633).
Thanks already for any assistance!
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
