Re: [alpine-devel] [PATCH] testing/sword: add new package
On Wed, Jul 23, 2014 at 08:19:36AM +0300, Timo Teras wrote:
> On Tue, 22 Jul 2014 21:01:42 -0700
> Isaac Dunham <ibid.ag_at_gmail.com> wrote:
> > On Tue, Jul 22, 2014 at 02:27:28PM +0200, Natanael Copa wrote:
> > > How about using /var/lib/sword as default and have a
> > > 'sword' group with write permissions there?
> > >
> > > They you can just add your users to the sword group to be able to
> > > install the data files.
> > >
> > That should work.
> > One question/minor issue:
> > abuild warns about chown in the post-install script.
> > But it would seem that there's no other sane way to make sure that
> > /var/lib/sword belongs to the "sword" group: to make it belong to
> > root:sword in the package, this group must exist when the package is
> > built and when it is extracted.
> > I presume pre-install could do the latter, but manipulating groups in
> > a build script is insanity.
> > If I can ignore that warning (assuming it belongs in abuild), I have a
> > script ready to go.
> > What's the preferred approach?
> Use pkgusers and pkggroups in APKBUILD, and do chown in the package()
> or subpkg split function. See 'transmission' or any other package with
> pkgusers in it for an example. And create the user in pre-install
> This allows apk to keep track of the file permissions properly.
> Doing chown in post-install would make the file permissions mismatch
> with what is in the apk database, and thus make 'apk audit' give
> spurious results.
Ok, thanks for the explanation. Patch should be incoming as soon as I've
built and tested it.
I might drop clucene as a build dependency, since sword seems to pick up
the libc regex interface. But I'd rather not do that right now.
Received on Tue Jul 22 2014 - 22:50:45 GMT