X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5C6815E46DE for ; Wed, 18 Aug 2004 11:39:55 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98119-06 for ; Wed, 18 Aug 2004 14:39:53 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id A12C35E46DC for ; Wed, 18 Aug 2004 11:39:51 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i7IEXkI9022324; Wed, 18 Aug 2004 10:33:46 -0400 (EDT) To: Alvaro Herrera Cc: Joe Conway , Steve Bergman , "Hackers (PostgreSQL)" , pgsql-admin@postgresql.org Subject: Re: [HACKERS] SRPM for 8.0.0 beta? In-reply-to: <20040818074959.GA25592@dcc.uchile.cl> References: <1092514982.19562.15.camel@voyager.localdomain> <411EFB9C.1090804@joeconway.com> <41210FE2.4020202@joeconway.com> <41226B6D.60503@joeconway.com> <17326.1092799454@sss.pgh.pa.us> <4122CCBE.6040505@joeconway.com> <20040818074959.GA25592@dcc.uchile.cl> Comments: In-reply-to Alvaro Herrera message dated "Wed, 18 Aug 2004 03:49:59 -0400" Date: Wed, 18 Aug 2004 10:33:45 -0400 Message-ID: <22323.1092839625@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/162 X-Sequence-Number: 14557 Alvaro Herrera writes: > Isn't there a way to generate this automatically? Why isn't the .spec > file (and the debian directory, for that matter) part of the source > tree? Can't speak for Debian, but Red Hat at least would not use such a spec file anyway. RH's procedures involve frequent addition of entries to the spec file's ChangeLog, so they keep package spec files separate from the "upstream" package tarball. Another good reason for keeping a separation is that the spec file may represent a package that aggregates multiple upstream packages. In the PG case a single specfile currently aggregates the core server, jdbc, and pygresql ... and I'm getting pressure to include more stuff. The init script is a different matter. That in principle could be taken from the upstream package. I'm not sure if all the Linux distributions could agree on a single init script, though --- I think the conventions vary somewhat across distros. regards, tom lane