[pgadmin-hackers] SVN Commit by dpage: r7019 - branches/REL-1_8_0_PATCHES/pgadmin3/pkg/redhat
Author: dpage Date: 2008-01-26 15:27:15 + (Sat, 26 Jan 2008) New Revision: 7019 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=7019view=rev Log: Updated Redhat spec file from Devrim Modified: branches/REL-1_8_0_PATCHES/pgadmin3/pkg/redhat/pgadmin3.spec.in ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] Synching RPM spec file with the community spec
On Jan 25, 2008 8:57 PM, Devrim GÜNDÜZ [EMAIL PROTECTED] wrote: Hi, On Fri, 2008-01-25 at 20:51 +, Dave Page wrote: https://projects.commandprompt.com/public/pgcore/browser/rpm/redhat/8.3/pgadmin3/F-9/pgadmin3.spec?format=raw This is the spec used in Fedora/EPEL and PGDG packages. Sure - but will it work on other platforms? ie. can I replace the mandrake, suse and redhat packaging directories with a single one for RPMs? I don't think so. I don't have SuSE and Mandrake around, but I think these specs may not work there. :-( Oh well - I've updated the file in the Redhat directory for 1.8.x and trunk. Thanks!! Regards, Dave ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Synching RPM spec file with the community spec
Hi. - Original Message - From: Dave Page [EMAIL PROTECTED] On Jan 25, 2008 8:57 PM, Devrim GÜNDÜZ [EMAIL PROTECTED] wrote: Hi, On Fri, 2008-01-25 at 20:51 +, Dave Page wrote: https://projects.commandprompt.com/public/pgcore/browser/rpm/redhat/8.3/pgadmin3/F-9/pgadmin3.spec?format=raw This is the spec used in Fedora/EPEL and PGDG packages. Sure - but will it work on other platforms? ie. can I replace the mandrake, suse and redhat packaging directories with a single one for RPMs? I don't think so. I don't have SuSE and Mandrake around, but I think these specs may not work there. I will check on SuSE, although change may be necessity. Regards, Hiroshi Saito ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match