Date: Sun, 11 Aug 2002 22:17:09 -0500 From: Ade Lovett <ade@FreeBSD.org> To: Will Andrews <will@csociety.org> Cc: Joe Marcus Clarke <marcus@FreeBSD.org>, <ports@FreeBSD.org>, <portmgr@FreeBSD.org> Subject: Re: Reserve uid:gid 92 Message-ID: <B97C92E5.17049%ade@FreeBSD.org> In-Reply-To: <20020812025447.GU78857@squall.waterspout.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/11/02 21:54, "Will Andrews" <will@csociety.org> wrote: > On Sat, Aug 10, 2002 at 12:11:20PM -0500, Ade Lovett wrote: >> How about a simple file maintained in ports/Mk/master.passwd.ports and >> ports/Mk/group.ports in the same form as etc/master.passwd and etc/group, >> with the addition of the port location? >> >> It shouldn't be too hard to then add a target to check for these at >> pre-install time and automaticall add them. > > That sounds ok, except I don't think ports/Mk is the right place > to put such a file. Well, I'm willing to be swayed a little, but I can also see a potential bikeshed moving it out of ports/ For example, let's suppose that <thing in base system> wants to use uid/gid 92 tomorrow as and when its imported. Then there's a clash. Who wins? I don't want to be a part of that mess. Put it in ports/Mk. Put it under portmgr@ control, and if there are any clashes, portmgr can speak offline with core, or srcmgr, or whatever. -aDe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B97C92E5.17049%ade>