[Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze

[Julien Danjou]

At 1262180806 time_t, Gerfried Fuchs wrote:
>  Why is it unique to use features only available in a later version?

Because you are dropping usability of your software for people running
earlier version.
In many case that is avoidable. In the Python world, many modules
support Python 2 and Python 3 using #ifdef, like Dimitri said. I hope
it's the same in the pg world.

>  This is the whole point of this thread: You won't be able to build and
> run it just fine in Debian because the package won't be there anymore at
> a certain point in time.

Removing a package should not impact the built modules source.

Again, when a Python version is removed from the Debian archive, we do
not ask all Python module maintainers to adapta their source. They all
depends on python-all-dev, which brings the correct Python version(s)
supported by Debian at that moment, and build the module against the
good version(s) of Python.

If Python version changes, a binNMU is triggered on affected packages,
which is damn faster and more efficient than mass filling bug reports.
Without a line change to the modules sources.

I do not see why this is not doable for PostgreSQL.

Cheers,
-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20091230/a3797578/attachment-0001.pgp>