pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg/52413 (pbulk as documented is broken)

The following reply was made to PR pkg/52413; it has been noted by GNATS.

From: Joerg Sonnenberger <>
To: John Klos <>
Subject: Re: pkg/52413 (pbulk as documented is broken)
Date: Mon, 17 Jul 2017 23:53:40 +0200

 On Mon, Jul 17, 2017 at 08:57:03PM +0000, John Klos wrote:
 > > Assign back. I have nothing to do with the wiki page and the setup described
 > > doesn't reflect any of the very basic configuration recommendations. It doesn't
 > > even include WRKOBJDIR and therefore requires a tree writable by the (unprivileged)
 > > build account.
 > While I agree that you're not responsible for documentation on the wiki, is
 > it reasonable that the default behavior of pbulk is to create an
 > unprivileged user, then try to compile with that user with the default build
 > location inside of the pkgsrc tree?
 pbulk itself doesn't even create a user.
 > Perhaps the build location's default in the context of pbulk should be
 > /usr/pbulk/tmp/. I think people should be able to chroot to a clean location
 > with a clean pkgsrc, then run:
 > sh /usr/pkgsrc/mk/pbulk/
 > /usr/pbulk/bin/bulkbuild
 I am not responsible for either.
 > without having to create an intermediate mk.conf or edit
 > /usr/pbulk/etc/mk.conf. Otherwise, what's the point of having a whole build
 > system with tools and configuration inside of /usr/pbulk?
 To have a consistent way to build the bulk build software itself and
 dependencies, without interacting with the to-be-build packages?
 > Back to this problem specifically, aside from adding WRKDIR to
 > /usr/pbulk/etc/mk.conf, what else nees to be changed to make this work out
 > of the box?
 Not /usr/pbulk/etc/mk.conf, /etc/mk.conf.

Home | Main Index | Thread Index | Old Index