ports/116448: devel/dbus intolerent of existing 556 GID
David O'Brien
obrien at FreeBSD.org
Wed Sep 19 06:20:47 PDT 2007
On Tue, Sep 18, 2007 at 11:55:25PM -0400, Joe Marcus Clarke wrote:
> On Tue, 2007-09-18 at 17:54 -0700, David O'Brien wrote:
> > On Tue, Sep 18, 2007 at 09:52:09PM +0000, marcus at FreeBSD.org wrote:
> > > Synopsis: devel/dbus intolerent of existing 556 GID
> >
> > > State-Changed-From-To: open->closed
> > > State-Changed-By: marcus
> > > State-Changed-When: Tue Sep 18 21:50:42 UTC 2007
> > > State-Changed-Why:
> > > 556 has been allocated to messagebus via /usr/ports/GIDs. If you absolutely
> > > need this GID for something else, you need to pre-create the messagebus
> > > group with a GID that works for you.
> >
> > This is disappointing - why must it be 556? The reason I had it already
> > defined is because the subversion install creates a 'svn' group and
> > doesn't specify a GID. To keep this from happening, why cannot we commit
> > /usr/ports/GIDs to /usr/src/etc/group to better reserve them?
>
> I think it was done this way as not all ports committers have src bits.
> Plus, not everyone installs all ports, so mandating UIDs and GIDs on all
> systems might be a waste. But as I said, you aren't restricted to 556.
> You can create a messagebus group before installing dbus, and the port
> will simply use that group with whatever gid you assign it.
I'm curious - why doesn't dbus then just use 'pw' to create the group
with an unspecified GID like the svn port does? Why was this so
anonying? I was trying to build evolution-exchange before going to work
- and of course the build broke 1/2 thru. Which I didn't notice until I
got home.
--
-- David (obrien at FreeBSD.org)
More information about the freebsd-gnome
mailing list