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 769E05E46E9 for ; Wed, 18 Aug 2004 13:10:37 -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 40876-06 for ; Wed, 18 Aug 2004 16:10:42 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3E4335E46E3 for ; Wed, 18 Aug 2004 13:10:34 -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 i7IGAKAZ000337; Wed, 18 Aug 2004 12:10:21 -0400 (EDT) To: Peter Eisentraut Cc: Alvaro Herrera , Joe Conway , Steve Bergman , "Hackers (PostgreSQL)" , pgsql-admin@postgresql.org Subject: Re: [HACKERS] SRPM for 8.0.0 beta? In-reply-to: <200408181755.21507.peter_e@gmx.net> References: <1092514982.19562.15.camel@voyager.localdomain> <20040818074959.GA25592@dcc.uchile.cl> <22323.1092839625@sss.pgh.pa.us> <200408181755.21507.peter_e@gmx.net> Comments: In-reply-to Peter Eisentraut message dated "Wed, 18 Aug 2004 17:55:21 +0200" Date: Wed, 18 Aug 2004 12:10:20 -0400 Message-ID: <336.1092845420@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/166 X-Sequence-Number: 14561 Peter Eisentraut writes: > Tom Lane wrote: >> In the PG case a >> single specfile currently aggregates the core server, jdbc, and >> pygresql ... and I'm getting pressure to include more stuff. > How does that compute, considering that everyone else appears to be > working on including less stuff? Well, *Marc* is working on including less stuff; the rest of us don't necessarily agree. In particular I've got to re-incorporate any major pieces that get removed from the core distribution, since people expect to find those in the RPM set. (In principle I suppose they could be handled as independent packages with independent specfiles, but so far the path of least resistance has been to keep 'em bundled together.) regards, tom lane