Re: SuSE RPMs available for PostgreSQL 7.4 - Mailing list pgsql-general

From Lamar Owen
Subject Re: SuSE RPMs available for PostgreSQL 7.4
Date
Msg-id 200311191218.29207.lowen@pari.edu
Whole thread Raw
In response to SuSE RPMs available for PostgreSQL 7.4  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: SuSE RPMs available for PostgreSQL 7.4  (Peter Eisentraut <peter_e@gmx.net>)
Re: SuSE RPMs available for PostgreSQL 7.4  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-general
On Wednesday 19 November 2003 11:59 am, Peter Eisentraut wrote:
> Lamar Owen writes:
> > Hey, Peter, for one who consistently complains about lack of consistency
> > in naming, you completely diregarded the precedent that has previously
> > been set for naming RPM releases (regardless of the source).

> These are SuSE RPMs.  They were build by SuSE following the conventions
> that SuSE has used for their past releases.  So who are we to argue with
> that?

The place they were put.  The 'customary place' has been
v{version}/RPMS/{distribution} so that they would be in
pub/binary/v7.4/RPMS/suse-{version}.  Their source RPM would go there too.  I
have no problem with the name of the RPM's themselves, just where they were
put.  As long as they don't have a PGDG in the release tag I'm happy with the
package names.

> > And then you neglected to put group write permissions on the directory so
> > that other binaries could be uploaded.

> I see

> drwxrwxr-x  3 petere  pgsql  512 Nov 17 20:47 binary/v7.4/
> If someone else put the group write permissions in there in between, I
> apologize.

I asked Marc to do it.

I would kindof liked a heads up on this; I had some plans for the RPMset that
I'm now going to delay.  But it is good for SuSE users to have something
there now, I agree.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC  28772
(828)862-5554
www.pari.edu


pgsql-general by date:

Previous
From: Oliver Elphick
Date:
Subject: Re: 7.4 broke psql
Next
From: Stephan Szabo
Date:
Subject: Re: defferable update & unique