Re: deprecating contrib for PGXN

On May 18, 2011, at 2:47 PM, Magnus Hagander wrote:

> I don't see why it couldn't, at least for a fair number of
> extensions.. It does require the ability to differentiate between
> patch releases and feature releases, though, which I believe is
> currently missing in pgxn (correct me if i'm wrong), but that's a
> solvable problem, no?

PGXN requires semantic versions. If authors use the correctly, then you can rely on the z in x.y.z to be a patch/bug
fixrelease, and the y and z to indicate new features. 

> Also, if it has several extensions, it should generate several DEB's -
> assuming they're independent extensions, right? If so, where's the
> problem?

Maybe they're not independent. But why is that a problem. There are a *lot* of DEBs with multiple Perl modules in them.

Best,

David