On 9/7/06, Fábio Mierlo <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to make a recipe for the Firebird database, it really sucks. > > There's 22K of patch until now, most of then is due hardcode "root" > strings.
Ouch. How are you patching that? It's interesting to make that modular so that the patch gets accepted by them, too. > The "make install" is the worst thing, it is interactive and change > a lot of files in /System/Settings. > > I don't look at recipes for others "server" applications, but what's > the rules for run daemon as non root? I haven't seen any task written for non-superusers yet, but I think you can safely grep for the user you expect to run with at /etc/passwd and then 'sudo' exec the daemon as that user if it exists. > And how to allow some installers add users, groups and change > some files in /System/Settings? That's a good question. We don't have a good way to do that now, but I think it should be addressed by both Compile and InstallPackage. I can think of something like Resources/{ExpectedUsers,ExpectedGroups} as a good solution.. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel