On 9/9/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> On Fri, 08 Sep 2006 02:38:51 +0200, 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.
>
> Can't you just do "find -type f | xargs -i sed -i s/root/0/ {}" in
> pre_patch()/pre_build()?
>
> >
> > 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?
> >
> > And how to allow some installers add users, groups and change
> > some files in /System/Settings?
> >
> For adding users and groups I usually use this in pre_build():
>
> if ! grep -q foo $goboSettings/group
> then
> Log_Normal "Adding group foo"
> groupadd foo
> fi
>
> if ! grep -q "foo:x:" $goboSettings/passwd
> then
> Log_Normal "Adding user foo"
> useradd foo -g foo -c 'added by Compile for Foo' -d $goboVariable/empty
> -s $goboExecutables/false
> fi
>
That is only useful in the recipe case. Packages wouldn't create the user.
> I'm still looking for a solution for apps that want to change things in
> current files in /System/Settings. If anyone have an idea, please shout.
>
At one point (before I ran out of free time), I was working on running
a R/PostInstall script through UnionSandbox. The idea was /P/App/1.0
would be rw and everything else would be redirected. Then a modified
UpdateSettings would merge it back based on user input.
Lucas's Resources/{ExpectedUsers,ExpectedGroups} would probably be
faster to implement and solve the most common case.
--
Carlo J. Calica
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
