--yrj/dFKFPuw6o+aM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Todd Vierling <tv@duh.org> wrote:
=20
> Will games also be fixed to add
>=20
> USE_PKGINSTALL=3Dyes
> PKG_GROUPS=3D${GAMEGRP}
>=20
> appropriately?

> If PKG_GROUPS were added where appropriate to auto-create the group (and
> perhaps MAKE_DIRS_PERMS to make /var/games for you), you could set a simp=
le
> default of GAMEGRP?=3Dgames in bsd.pkg.mk and not worry about opsys-speci=
fic
> changes unless a specific opsys needs an override.

Hmmm.  Yes, I see your point.  What is our current policy or what do
people think:  do we want pkgsrc to add users as pkgsrc sees fit, or
should we rely on the system administrator to set variables according to
their preference?

I'd be inclined towards to latter, but I understand the former, too.  We
already to create users for other packages, right?


> On a related note:  GAMEOWN should default to ${BINOWN} -- or ideally, not
> be configurable separately from ${BINOWN} at all.

Well, it does default to BINOWN if SETGID is not set.  I just noticed
that /var/games contains a number of files owned by the user 'games', so
somewhere along the lines somebody thought that the user 'games' is
useful.  Though I have no objection to removing this, as I agree that
there shouldn't be any use for that user if the binary is setgid.

-Jan

--=20
DON'T PANIC!

--yrj/dFKFPuw6o+aM
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAot9bfFtkr68iakwRAlH6AKDQtfr5jVESDKOHKL9xa9vTJ2BfZgCg54+f
rsyhByDySrX63BI115akXkA=
=nOSt
-----END PGP SIGNATURE-----

--yrj/dFKFPuw6o+aM--