GNU bug report logs - #32297
[PATCH] make postgresql find its plugins

Previous Next

Full log

Message #11 received at 32297 <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: 32297 <at> debbugs.gnu.org
Subject: Re: [PATCH] make postgresql find its plugins
Date: Fri, 14 Sep 2018 22:03:53 +0200

[Message part 1 (text/plain, inline)]

Le Fri, 14 Sep 2018 17:29:19 +0200,
Gábor Boskovits <boskovits <at> gmail.com> a écrit :

> This looks good to me.
> 
> The extensions field is a good idea.
> 
> I also believe that after adding an extensions field it would be
> easier to document this.

Here is a new series of 2 patches: the first one is unchanged (only
rebased to master) and the second one introduces the extensions field
and documents it. I added an example in the documentation.

> 
> Do you think that it might be possible to list these extension
> packages somehow, or even stop them being directly installable,
> noting to use the extensions field in your service definition? Would
> that make sense?

Extension packages still have to be visible for users to list them in
the new field, so it seems hard to hide them at the same time :) I
agree it would make sense to be able to list all such extensions, and
so is listing extensions to other packages. Maybe we can think of a
generic mechanism for that?

[0001-gnu-postgresql-Fix-finding-extensions.patch (text/x-patch, attachment)]

[0002-gnu-postgresql-Add-extensions.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.