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

Re: [HACKERS] Re: [PORTS] RedHat6.0 & Alpha

From: "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>
To: Ryan Kirkpatrick <rkirkpat(at)nag(dot)cs(dot)colorado(dot)edu>
Cc: pgsql-ports(at)postgreSQL(dot)org, Postgres Hackers List <hackers(at)postgreSQL(dot)org>, debian-alpha(at)lists(dot)debian(dot)org
Subject: Re: [HACKERS] Re: [PORTS] RedHat6.0 & Alpha
Date: 1999-07-30 22:53:59
Message-ID: 199907302253.XAA27690@linda.lfix.co.uk (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-ports
Ryan Kirkpatrick wrote:
...
  >	Actually, I am working with the 6.5.1 tarball, for the simple
  >reason that I want a set of patches I can post on the debian-alpha mailing
  >list, along with the instructions to grab the 6.5.1 tarball from
  >ftp.postgresql.org, apply patches, configure, compile, install, and they
  >are set to go (No need to do a CVS pull, etc).

Hi Ryan,
I'm at a disadvantage here, because I don't have an Alpha and rely on
others on debian-alpha to get postgresql packages compiled for Alpha.
Thanks for your efforts on this.

I just want to comment on what you are saying about generating a Debian
source package.  There will be a problem, because you are proposing to
provide source that will be different from the main 6.5.1 source; however,
the Debian archive assumes that source is identical across all architectures.
This means that the Alpha source for PostgreSQL must not be uploaded to the
Debian archive because it will replace the source for all other 
architectures.

If this were to be a permanent problem, it could be addressed by renaming
the packages; however, this would cause a lot of trouble to many users,
so I don't want to do that when 6.6 will remove the need for it.

What I propose to do is to disable the Alpha build in the next version of
the Debian package (6.5.1-4) and make it put out information that the
Alpha source must be downloaded from <somewhere>.  I would prefer that to be
in my account at www.debian.org, so that I can incorporate any changes
that go into the mainstream package.



As to producing the Alpha packages, the procedure should go something
like this:

1. Patch postgresql-6.5.1.orig (i.e. postgresql as provided at ftp.postgresql.org).

2. Examine the patches in the latest debian postgresql-6.5.1-x.diff.gz
(where x is the latest Debian release) and merge everything that does
not conflict with the new Alpha patches.

3. Update the version number in debian/changelog to 6.5.1-x.0.1alph and
build the binary packages.

4. Upload the binary packages only.

5. Put the source package in my account (and make sure I have permission
to write it!).



-- 
      Vote against SPAM: http://www.politik-digital.de/spam/
                 ========================================
Oliver Elphick                                Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight                              http://www.lfix.co.uk/oliver
               PGP key from public servers; key ID 32B8FAA1
                 ========================================
     "And Samuel said, Hath the LORD as great delight in 
      burnt offerings and sacrifices, as in obeying the 
      voice of the LORD? Behold, to obey is better than 
      sacrifice, and to hearken than the fat of rams."      
                                     I Samuel 15:22 



Responses

pgsql-ports by date

Next:From: Tom LaneDate: 1999-07-30 23:05:03
Subject: Re: [HACKERS] Patches for Postgresql on Linux/Alpha!
Previous:From: Tatsuo IshiiDate: 1999-07-30 21:37:16
Subject: Re: [HACKERS] Patches for Postgresql on Linux/Alpha!

pgsql-hackers by date

Next:From: Tom LaneDate: 1999-07-30 23:05:03
Subject: Re: [HACKERS] Patches for Postgresql on Linux/Alpha!
Previous:From: Tatsuo IshiiDate: 1999-07-30 21:37:16
Subject: Re: [HACKERS] Patches for Postgresql on Linux/Alpha!

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