tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]


On Fri, Dec 17, 2010 at 10:41:03AM -0500, Greg Troxel wrote:
> Joerg Sonnenberger <> writes:
> > On Fri, Dec 17, 2010 at 09:02:35AM +0100, Adam wrote:
> >> Before I commit the update for PostgreSQL packages, I would like to
> >> change their PKGNAME to postgresql-xxx instead of postgresql90-xxx,
> >> postgresql83-xxx, postgresql82-xxx. The same way as MySQL packages
> >> are named. 
> >
> > Please do NOT change the package name like that. Just because e.g. PHP
> > and MySQL want to create a major hassle isn't an argument to do it for
> > sane software as well.
> Do you object to the act of changing, or to the new state?  Could you
> explain the 'major hassle'?

Both, but primarily the new state. It basically requires any pattern an
explicit limit if you don't want to get surprised when a new Postgres
version arrives. In the real world, a Postgres update requires at least
some planing to deal with the database format change, if nothing else.


Home | Main Index | Thread Index | Old Index