On Wed, Nov 19, 2003, Tres Seaver wrote:
> On Wed, 2003-11-19 at 10:08, Thomas Lotterer wrote:
> > On Tue, Nov 18, 2003, Tres Seaver wrote:
> >
> > > I have banged around a bit further on the OpenPKG specfile I wrote for
> > > Zope, but still can't figure out how to use %{l_rpmtool} to get the
> > > ownership / attributes set properly for the "data" directory. [...]
> > >
> > Tres,
> > i tried the following spec and results look good and as expected.
> >
> Odd, I don't get that when running from OpenPKG 1.3.1 (I had to modify
> your spec to make the prereq work)::
>
Oops, sorry, didn't notice you are on RELEASE.
> $ uname -a
> SunOS blade 5.8 Generic_108528-13 sun4u sparc SUNW,Sun-Blade-100
> $ rpm -qa
> [...]
> openpkg-1.3.1-1.3.1
> [...]
>
> Interestingly, if I install the test package as root, the ownership is
> set correctly, which is my clue: the Zope package also installs with
> correct ownership when rpm runs as root, rather than the 'cw' user
> (which makes sense, I guess).
>
Yep. When building packages as unprivileged user OpenPKG/RPM try hard
to cheat when it comes to setting dir/file owner/group/perms which
are beyond that unprivileged user's scope. It does so by working with
normal perms and poking the out-of-scope perms into the (embedded cpio)
archive.
When it comes to installing such a package the manipulated perms in the
archive become reality assumed the installing user has the power to make
it happen. In such cases root access is required. Works as designed.
--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
