On Thu, Mar 14, 2013 at 07:52:31AM -0400, Alon Bar-Lev wrote:
----- Original Message -----
> From: "Jiri Belka" <jbelka(a)redhat.com>
> To: "Alex Lourie" <alourie(a)redhat.com>
> Cc: engine-devel(a)ovirt.org, users(a)ovirt.org
> Sent: Thursday, March 14, 2013 1:47:12 PM
> Subject: Re: [Users] Migrating engine-setup to otopi
>
> On Thu, 14 Mar 2013 07:06:04 -0400 (EDT)
> Alex Lourie <alourie(a)redhat.com> wrote:
>
> > > > 1. Be able to port engine to other distributions.
> > >
> > > Really? Beside this topic I see hardcoded usernames in scripts...
> > >
> > >
http://gerrit.ovirt.org/#/c/12551/2/backend/manager/dbscripts/dbfunctions...
> >
> > These usernames are not hard-coded. There are default values
> > present which are kept for
> > local installations, but with remote DB setup the user is prompted
> > to provide a username
> > of her/his own.
>
> Not everywhere are postgresql dirs owned by postgres, on some BSDs it
> is
> _postgresql.
Right, as I said this is going away.
I am porting this first to Gentoo, which is the most complex, then I
will be able to provide debian based.
Would it be useful to start to provide an ovirt-overlay for this? I
already started
https://github.com/ekohl/ovirt-overlay where I packaged
ovirt-shell and its dependencies (including ovirt-sdk-python). I'd be
happy to extend this with more packages based on the info available on
http://wiki.gentoo.org/wiki/OVirt.