Обсуждение: FreeBSD PostgreSQL7 port and v7.0.2
Hi: First, is there a (free) version of JSQL available for Postgresql 7? Can anyone direct me to a vendor/website/documentation? *************************************************************** I am running FreeBSD 4.0-STABLE (i386). I want to install PostgreSQL v7.0.2 but the port maintainer is unable to update it (he writes: "I'm busy until 2000/06/27 because of CCIE certification.") The current FreeBSD port is: v7.0.0. The changes to the alter the Postgresql v7.0.0 FreeBSD port to install v7.0.2 instead would appear to be trivial but, having never done this before, I just wanted to check. 1. I changes all references of "7.0.0" to "7.0.2" in the Makefile 2. I changed the MD5 file to reflect the MD5 checksums for 7.0.2 Is there anything else that I need to do or be aware of before making the port? (Frankly, I would be surprised if there is any need to change the v7.0.0 patches to make v7.0.2 work under FreeBSD.) * * * NOTE * * * I have been told that I should double check the list of files in the distribution as the PLIST file in the port needs this. I know that some files were missing in 7.0.1 BUT THAT IS INCONSEQUENTIAL in my case since I am working off 7.0.0 port files. Were there any changes in the list of files between the 7.0.0 distribution and the 7.0.1 distribution? (additions and deletions ONLY, not changes within the files) ALSO NOTE: I don't blame the port maintainer for not having the time to do the update. While the changes appear simple, I'm sure that the requiste testing requires a block of time that he doesn't have at this time. I just can't wait for three weeks or more to install PostgreSQL7, and I would like the latest version. John ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
John Daniels wrote: > > (After I have installed 7.0.2, I will send a diff and comments to the port > maintainer to help him when he updates the port.) John, Since Andreas is busy for so long, I'd suggest you send-pr your patches so people can upgrade postgres before he gets back and commits them. Thanks! -- Palle
On Thu, 8 Jun 2000, John Daniels wrote: > Hi: > > > > Thanks, I check into that. I have assumed, from my own reading of > > > the release history, that: > > > > > > 1) 7.0.1 fixes some minor bugs, and > > > 2) 7.0.2 was released so quickly after 7.0.1 because some > > > documentation was left out as an oversight (which was probably > > > already in of 7.0.0). > > > > > > Which led me to conclude that: > > > 1) there should be no change to the patches that make 7.0.x > > > run with FreeBSD > > > 2) there are no new files from 7.0.0 to 7.0.2 > > > >the only caveat to 2 ... there are now docs, which we missed > >including in v7.0.1 ... are those installed anywhere? > > FreeBSD currently has a port (in the ports collection) of v7.0.0. There has > not been a port of v7.0.1. I am trying to edit the v7.0.0 port so that it > will install v7.0.2. My assumptions, listed above, lead me to beleive that > this should be fairly easy to do. > > I am not the port maintainer (he is busy until the end of the month, as > described in my previous post), and I have not previously created or > customized a port, so I am trying to get more info from people, like > yourself, who are more knowledgeable about ports or Postgresql. > > The crucial question at this point seems to be: has there been any change in > the number and names of postgresql files from v7.0.0 to v7.0.2? v7.0.1 is > inconsequential since I am editing/customizing a port that works for v7.0.0. Installed, no ... in fact, I can't think of the last time anything was added to the number of files installed ... > (After I have installed 7.0.2, I will send a diff and comments to the port > maintainer to help him when he updates the port.) > > John > > P.S. My mail to pgsql-general@postgresql.org doesn't seem to be getting > through. Would you have any idea why this is so? Are you subscribed to the list? its a closed list, subscribers-only ... we're using majordomo2, so you can do a 'subscribe-nomail' so that you can post but not get any messages back ...