On 9/13/07, Hisham Muhammad <[EMAIL PROTECTED]> wrote: > On 9/13/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > On 9/13/07, Hisham Muhammad <[EMAIL PROTECTED]> wrote: > > > CVSROOT: /sources/goboscripts > > > Module name: tools > > > Changes by: Hisham Muhammad <hisham> 07/09/13 23:29:37 > > > > > > Modified files: > > > BuildLiveCD/bin: MakeSystemSettings > > > > > > Log message: > > > Add missing groups > > > > While you're on it, I remember having problems with the shipped DBus > > package due to missing messagebus (or was it dbus?) user/group.. > > What's the best way to deal with these packages that require special > > user/groups? Should we just have them by default in passwd/group? > > That's a good question. I noticed some problems today caused by our > use of the Gentoo udev rules; they had some groups like "cdrw" and > "usb". I simplified the rules to use more generic groups like "cdrom". > Still, I peeked into an Ubuntu system and they do have lots of groups > there. > > I'm guessing shipping as many predefined groups as possible would keep > things simple with regard to maintenance and compatibility. I didn't > copy the whole bunch of groups from other distros, but I wonder if > that wouldn't be beneficial. > > I understand that conceptually having less groups is cleaner, but > fighting an uphill battle against a lot of packages expecting groups > to be there is not worth it. The existance of all these groups can > normally be just ignored in normal desktop use, anyway.
Ok, I second that. I'll ensure to add any missing group required by packages in the iso to the cvs. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
