On Tue, 9 Jun 2009 19:21:48 +0200, Emanuele Pucciarelli <ep at acm.org> wrote:
> Hi Steven,
>
> Currently there's no way to do this. I have contributed a set of
> patches for pkgbuild that allow arbitrary actions, including new users
> and groups, inside a spec file. While not a top-priority item, I think
> this integration is already on Laca's to-do list; once that is done, I
> guess it will not take too much to make the patched pkgbuild available
> to SourceJuicer too.
>
> If you want to have that for your own repo, in the meantime, get the
> patch from the list archives, or just ping me and I'll dig it up and
> send it to you :)
Certainly. I think for now I may be able to work around the issue simply by
having the files owned by root:bin and providing additional instructions in
the %description. Unfortunately I do not have much non-ON bandwidth to
spend, although I am more than happy to post my initial specfile to jucr if
others wish to hack on it as new features of pkgbuild become available.
>> 2) A huge number of files are installed which rely on very specific
>> permissions (i.e. setuid root, with the newly created group name) and
>> many
>> files require they be installed with the new user/group.
>> 3) %files is growing out of control because how dissimilar permissions
>> are
>> on each file.
Meh. A /usr/share/amanda/post-install.sh script may just appear in the
package :) Although, I suppose it is possible to provide the inetconv
results of the new inetd.conf entry as an additional Source - I doubt there
is much hope of automating this from within pkgbuild.
>> 4) A few sparse directories should be installed (notably /var/amanda,
and
>> /etc/amanda) - there is an earlier thread on this list questioning how
to
>> create these correctly using pkgbuild.
>
> I must have missed that. I haven't run into any problem with that so
> far, will try to catch the thread again.
Perhaps I am not doing something correctly, I have been following the
pattern of:
%install
...
mkdir -p ${RPM_BUILD_ROOT}/foo
%files
%dir %attr (...) foo
Thanks again!
Steve
--
Yet magic and hierarchy
arise from the same source,
and this source has a null pointer.
Reference the NULL within NULL,
it is the gateway to all wizardry.
