Re: new postgresql package

[Carnë Draug]

On 11 January 2013 23:56, Olaf Till <address@hidden> wrote:
> can I maintain my postgresql package at forge?

On 12 January 2013 09:15, Olaf Till <address@hidden> wrote:
> I had roughly scanned the database package and decided to start from
> scratch. Merging with 'database' would now mean to replace its
> postgresql part.

Yes, but I would also prefer you placed your code as part of the
current database package. Doesn't mean that the current package that
deals with postgreSQL needs to use it. Is it not not possible to have
your postgreSQL specific functions to exist side by side with the
functions from that package? If not, then their names would have to be
changed even if on another package to avoid problems in the case
someone has the two packages installed.

> Do you know the database package well? From what I read in the list I
> thought it does not work now. Is that not true?

The database package still compiles with Octave 3.6.X (at least on my
system) but there are other issues with the database package,
including license. While the DESCRIPTION claims to be under GPL2 and
BSD, this is not completely true when one actually looks at the
individual files. Of course, compiling doesn't mean it works well.

On 12 January 2013 15:12, Olaf Till <address@hidden> wrote:
> I would not like to mix maintained code with unmaintained in
> one package.

You don't have to maintain the rest of the code. Package maintainer
does not mean you'll have to fix all bugs related to the package. Not
even code author means you have to. But it means less packages around.

Of course, that's up to you. If you do not want to, feel free to go
ahead and create a database-postgreSQL package on octave-forge/main

Carnë