Skip site navigation (1) Skip section navigation (2)

Re: RPMs built for Mandrake

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RPMs built for Mandrake
Date: 2000-08-01 15:45:58
Message-ID: 3986F0B6.2F09893D@wgcr.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Thomas Lockhart wrote:
>   ftp://ftp.postgresql.org/pub/binary/Mandrake/
 
> The Mandrake/ directory will move to /pub/binary/v7.0.2/Mandrake once
> the permissions are fixed up: Lamar, can you please adjust the group
> permissions to allow pgsql to write into those directories (and to move
> around files, just in case)? Should we adjust the names on the
> directories from RPM and redhat-RPM to "redhat" only (or "RedHat" or ??)
> to get some symmetry with the other distros?

Well, what I had in mind was have a unified RPM tree, single SRPM, with
multiple binary RPM trees.  So, since someone else has fixed the group
perms on that tree already (thanks Jeff or Marc), pop the Mandrake
binary RPMs into pub/binary/v7.0.2/RPM/RPMS/mandrake-7.x (the dir is
already created).

If there had been departures from the main RPMset source RPM, then we
would need the source RPM as well uploaded -- but, as long as the build
is simply a rpm --rebuild (or equivalent), then there's no need to use
the space for an essentially identical file.

If you want to follow Mandrake naming conventions (-2mdk) that's fine,
but not necessary as being in the 'mandrake-7.x' dir should set them
apart.

As to a new RPM version, yes on both interpretations -- there is/will be
a new version of the PostgreSQL RPM's before the next major PostgreSQL
release, and there will also be a new major version of RPM itself before
the next major PgSQL release.  The RPM's from the public RedHat beta
release should, until I post newer ones, be considered the current
version -- and, since the release of the public beta, I will be posting
newer RPM's this week.

As a matter of necessity, you will be needing to upgrade to RPM 3.0.5 to
do any RPM building from these src RPMs in the future, more than
likely.  And, if you want to poke around with the src RPM from the
RedHat beta, you will have to upgrade to RPM 3.0.5 in order to even read
the src rpm, as the RedHat beta is using RPM 4.0-format RPMs.  RPM 4.0
should be in a released state by the time PgSQL releases a new major
version.  And I can now say that since the beta is public ~;-).  So, you
should be seeing more updates to the RPMset now.

And I want to give many kudos and thanks to Trond Eivind Glomsrød, who
has been shepherding the RPMset through the labyrinthine update publicly
known as Pinstripe.

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2000-08-01 16:02:36
Subject: random() function produces wrong range
Previous:From: Philip WarnerDate: 2000-08-01 13:37:04
Subject: Re: pg_dump & performance degradation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group