Fwiw, I'm not saying packages must not use the postgresql namespace, I'd just
leave it to the maintainer to decide.
Martin Pitt schrieb:
Hello Ansgar, Christoph,
Christoph Berg [2012-08-01 21:12 +0200]:
> The various postgresql-* packages are mostly plugins (PL/something)
Right, postgresql-
Hello Ansgar, Christoph,
Christoph Berg [2012-08-01 21:12 +0200]:
> The various postgresql-* packages are mostly plugins (PL/something)
Right, postgresql-X.Y-foo are server-side plugins which are specific
to a major PostgreSQL server version. They need to be versioned just
like PostgreSQL itself
I usually prefer packages to use the upstream name so they are easy to find
(think other distributions).
The various postgresql-* packages are mostly plugins (PL/something) which
follow the example of postgresql-plperl-x.y (built from PG core). For real
applications like barman, that's not real
On 08/01/2012 11:18 AM, Roger Leigh wrote:
> On Wed, Aug 01, 2012 at 09:56:56AM +0200, Marco Nenciarini wrote:
>>
>> * Package name: barman
>
> postgresql-barman would make it a bit easier for people to find.
> Most of the other postgreql packages use the postgresql- namespace.
The postgresql
On Wed, Aug 01, 2012 at 09:56:56AM +0200, Marco Nenciarini wrote:
>
> * Package name: barman
postgresql-barman would make it a bit easier for people to find.
Most of the other postgreql packages use the postgresql- namespace.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux
Package: wnpp
Severity: wishlist
Owner: Marco Nenciarini
* Package name: barman
Version : 1.0.0
Upstream Author : 2ndQuadrant Italia (Devise.IT S.r.l.)
* URL : http://www.pgbarman.org/
* License : GPL
Programming Lang: Python
Description : Backup and R
6 matches
Mail list logo