public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron W. Swenson" <titanofold@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Eclasses: postgres and postgres-multi
Date: Tue, 12 Jan 2016 16:53:29 -0500	[thread overview]
Message-ID: <20160112215328.GC2008@gengoff.gsmr1.local> (raw)
In-Reply-To: <569568CE.6040404@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]

On 2016-01-12 21:57, Manuel Rüger wrote:
> On 12.01.2016 20:22, Aaron W. Swenson wrote:
> > There are several ebuilds that repeat the same checks and need to
> > perform the same duties when it comes to working with PostgreSQL. For
> > example, making sure the users' currently slot is compatible with the
> > ebuild requirements. postgres.eclass addresses this and has
> > additional conveniences to build a dependency string and add a new user
> > into the postgres system group.
> > 
> > Additionally, as most of you are aware, we have a slot capable
> > dev-db/postgresql. There is some difficulty that needed to be resolved
> > so that extensions could also be installed into multiple slots, which is
> > addressed by postgres-multi.eclass.
> > 
> > I've an overlay at:
> > https://github.com/titanofold/titanofold-gentoo-x86
> > 
> > With the pgsql-eclass branch containing the eclass and a postgres-multi
> > enabled PostGIS.
> > 
> > Naturally, the eclasses work for me, so far.
> > 
> > For your convenience, I've also attached the eclasses.
> > 
> 
> You might wanna add some quotes around the variables in that line:
> enewuser $1 $2 $3 $4 ${groups}
> 
> Cheers,
> 
> Manuel
> 

Done.

https://github.com/titanofold/titanofold-gentoo-x86/commit/976455582c95d62ed7ee5c102e58948a4afb037c

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 345 bytes --]

  reply	other threads:[~2016-01-12 21:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 19:22 [gentoo-dev] New Eclasses: postgres and postgres-multi Aaron W. Swenson
2016-01-12 20:57 ` Manuel Rüger
2016-01-12 21:53   ` Aaron W. Swenson [this message]
2016-01-13 16:11     ` Ian Stakenvicius
2016-01-15 16:43       ` Aaron W. Swenson
2016-01-15 17:43         ` Ian Stakenvicius
2016-01-15 18:26           ` Ian Stakenvicius
2016-01-15 19:24           ` Aaron W. Swenson
2016-01-22 16:51             ` Ian Stakenvicius
2016-01-22 20:11               ` Aaron W. Swenson
2016-01-23 15:51                 ` Ian Stakenvicius
2016-01-25 15:31                   ` Ian Stakenvicius
2016-01-26 11:06                     ` Aaron W. Swenson
2016-01-24 23:29 ` Aaron W. Swenson
2016-01-24 23:44   ` Michael Orlitzky
2016-01-25 12:29     ` Aaron W. Swenson
2016-01-26  3:34       ` [gentoo-dev] " Jonathan Callen
2016-01-26 11:14         ` Aaron W. Swenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160112215328.GC2008@gengoff.gsmr1.local \
    --to=titanofold@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox