On Wed, May 11, 2011 at 22:05, David E. Wheeler <david@kineticode.com> wrote:
> On May 11, 2011, at 12:55 PM, Cédric Villemain wrote:
>
>> I though cpan has something to track the modules built locally and
>> update them all. As probably have pgxn (if cpan has) or will have at
>> some point. Am I wrong ?
>
> Not sure what you mean by this. Daniele Varrazzo has been writing a PGXN client, though. Are you thinking of
somethinglike
>
> pgxn update all
>
> That would install the latest version of all installed extensions?
Well, what's needed for the infrastructure is:
* A munin/nagios compatible monitor that will alert when *security or
other critical updates* are avaiable. It should *not* fire off alerts
if it's just a new feature release, we're only interested in patches.
* A "pgxn update all" command like the one you mentioned, but one that
again only deals with patches and security updates, not new versions.
We want to be able to basically automate monitoring and updating
*without* risking compatibility problems.
IIRC you can't do that with CPAN today for example, which is why
people tend to prefer to rely on the DEB packaged CPAN modules,
because then the packager takes on the responsibility to backpatch
fixes.
> As for packaging what's on PGXN, I've discussed a bit with Daniele, Magnus, and Devrim (via Twitter) the idea of
havingsome kind of automated way for PGXN distributions to automatically be repackaged for RPM and/or .deb and/or
StackBuilderdistribution.
Yeah, that's definitely something that would be *very* useful.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
