How do we create the releases?

Hi Marc,

Is there a written procedure about creating tarballs? I'd like to start
working on 8.3 RPMs and I want to know what I should to to create a
tarball.

Regards,
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Tuesday, June 05, 2007 10:28:58 +0300 Devrim GÜNDÜZ
<devrim(at)CommandPrompt(dot)com> wrote:

>
> Hi Marc,
>
> Is there a written procedure about creating tarballs? I'd like to start
> working on 8.3 RPMs and I want to know what I should to to create a
> tarball.

Just a script ... relevant bits:

/usr/bin/cvs -d /cvsroot -q export -rREL7_3_19 pgsql
cd pgsql
./configure
cd doc/src
gmake postgres.tar.gz
mv postgres.tar.gz ..
gmake postgres.tar.gz
mv postgres.tar.gz ..
gmake man.tar.gz
mv man.tar.gz ..
cd sgml
gmake HISTORY INSTALL
mv -f HISTORY INSTALL ../../..
cd ../../..
gmake split-dist=yes dist
gmake maintainer-clean

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFGZzuZ4QvfyHIvDvMRAij1AKDWTwj6DZWthxvuEIZE6P1PoGDHcgCg2tV/
IR2CdNIokfs363FGifAklUY=
=tcIx
-----END PGP SIGNATURE-----

On Wed, Jun 06, 2007 at 07:56:25PM -0300, Marc G. Fournier wrote:
> - --On Tuesday, June 05, 2007 10:28:58 +0300 Devrim GÜNDÜZ
> <devrim(at)CommandPrompt(dot)com> wrote:
>
> >
> > Hi Marc,
> >
> > Is there a written procedure about creating tarballs? I'd like to start
> > working on 8.3 RPMs and I want to know what I should to to create a
> > tarball.
>
> Just a script ... relevant bits:

<snip>

Is this script in CVS somewhere? I know it's not in the main backend repo.
But we shuold keep it either there or somewhere else - perhaps the pmt
repository?

//Magnus

Magnus Hagander wrote:
> Is this script in CVS somewhere? I know it's not in the main backend
> repo.

Most of what these scripts have done in the past has been systematized
and folded into the "make dist" target in the mean time, and AFAICT, we
could integrate the documentation preparation as well, now that it
works automatically in a reliable fashion. That would reduce the
answer to the original question to something like

./configure
make dist[check]

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

On Thu, Jun 07, 2007 at 01:12:06PM +0200, Peter Eisentraut wrote:
> Magnus Hagander wrote:
> > Is this script in CVS somewhere? I know it's not in the main backend
> > repo.
>
> Most of what these scripts have done in the past has been systematized
> and folded into the "make dist" target in the mean time, and AFAICT, we
> could integrate the documentation preparation as well, now that it
> works automatically in a reliable fashion. That would reduce the
> answer to the original question to something like
>
> ./configure
> make dist[check]

If we can do that, that makes it even better. But is it something we can
reasonably backpatch? Otherwise we still need both documentation and
scripts to deal with back branches.

//Magnus

Hi,

On Thu, 2007-06-07 at 13:12 +0200, Peter Eisentraut wrote:
> make dist[check]

AFAIK "make dist" does not prepare postgres.tar.gz.

Regards,
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Thursday, June 07, 2007 14:22:22 +0300 Devrim GÜNDÜZ
<devrim(at)CommandPrompt(dot)com> wrote:

> Hi,
>
> On Thu, 2007-06-07 at 13:12 +0200, Peter Eisentraut wrote:
>> make dist[check]
>
> AFAIK "make dist" does not prepare postgres.tar.gz.

right, as peter originally said, 'make dist' *could* incorporate the steps that
right now lead up to 'make dist' (ie. build the docs) ...

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFGaB3E4QvfyHIvDvMRAgqRAJ4ln2cGOdPzcNzlbnjCnmMyZsU2tgCeO677
IbDu8XpIqts1wy04JAk6lwI=
=Zjhp
-----END PGP SIGNATURE-----

Magnus Hagander wrote:
> On Thu, Jun 07, 2007 at 01:12:06PM +0200, Peter Eisentraut wrote:
>> Magnus Hagander wrote:
>>> Is this script in CVS somewhere? I know it's not in the main backend
>>> repo.
>> Most of what these scripts have done in the past has been systematized
>> and folded into the "make dist" target in the mean time, and AFAICT, we
>> could integrate the documentation preparation as well, now that it
>> works automatically in a reliable fashion. That would reduce the
>> answer to the original question to something like
>>
>> ./configure
>> make dist[check]
>
> If we can do that, that makes it even better. But is it something we can
> reasonably backpatch? Otherwise we still need both documentation and
> scripts to deal with back branches.

Marc, how's this coming? We still need this documented somewhere, if
it's not being put into CVS. And documenting what it is could be a good
starting point for somebody else to put it into the Makefile, if you
don't have the time to work on that part yourself.

But not having it documented *or* in the Makefile just sucks...

//Magnus

On Saturday 23 June 2007 05:56, Magnus Hagander wrote:
> Magnus Hagander wrote:
> > On Thu, Jun 07, 2007 at 01:12:06PM +0200, Peter Eisentraut wrote:
> >> Magnus Hagander wrote:
> >>> Is this script in CVS somewhere? I know it's not in the main backend
> >>> repo.
> >>
> >> Most of what these scripts have done in the past has been systematized
> >> and folded into the "make dist" target in the mean time, and AFAICT, we
> >> could integrate the documentation preparation as well, now that it
> >> works automatically in a reliable fashion. That would reduce the
> >> answer to the original question to something like
> >>
> >> ./configure
> >> make dist[check]
> >
> > If we can do that, that makes it even better. But is it something we can
> > reasonably backpatch? Otherwise we still need both documentation and
> > scripts to deal with back branches.
>
> Marc, how's this coming? We still need this documented somewhere, if
> it's not being put into CVS. And documenting what it is could be a good
> starting point for somebody else to put it into the Makefile, if you
> don't have the time to work on that part yourself.
>
> But not having it documented *or* in the Makefile just sucks...
>

And while we're talking about things that suck wrt packaging, I noticed it's
now been over a year since I first complained about the stable snapshots in
our ftp directory being outdated
(http://www.postgresql.org/ftp/stable_snapshot/) if no one is going to fix
that, can we remove them?

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

Robert Treat wrote:
> And while we're talking about things that suck wrt packaging, I noticed it's
> now been over a year since I first complained about the stable snapshots in
> our ftp directory being outdated
> (http://www.postgresql.org/ftp/stable_snapshot/) if no one is going to fix
> that, can we remove them?

They look current now.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +