FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 08-04-2012, 05:02 PM
Ansgar Burchardt
 
Default postgresql-* package namespace

Martin Pitt <mpitt@debian.org> writes:
> 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 for upgrades, parallel installability, etc.

Well, it is *either* postgresql-X.Y-foo *or* postgresql-foo-X.Y right
now. I was wondering if we should try to use only one of these two
schemes.

Ansgar


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87y5lu8uan.fsf@deep-thought.43-1.org">http://lists.debian.org/87y5lu8uan.fsf@deep-thought.43-1.org
 
Old 08-04-2012, 10:00 PM
Christoph Berg
 
Default postgresql-* package namespace

Nod. We do have some weirdness there. The schema is that packages built from postgresql itself use postgresql-*-x.y (mostly), and all others use postgresql-x.y-*. Arguably, that's confusing.



I have some plan in the back of my brain that extension modules should ship .so files for all postgresql versions they support in one single binary package. That would get rid of most of the versioned packages with minimal space overhead (the .so files are usually pretty small, with lots of common files in /usr/share).
 

Thread Tools




All times are GMT. The time now is 01:38 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org