ports/166534: finance/openerp-server, finance/openerp-web: OpenERP misconfiguration

[Michael Scheidell]

The following reply was made to PR ports/166534; it has been noted by GNATS.

From: Michael Scheidell <scheidell at FreeBSD.org>
To: <bug-followup at FreeBSD.org>
Cc:  
Subject: Re: ports/166534: finance/openerp-server, finance/openerp-web: OpenERP
 misconfiguration
Date: Tue, 17 Apr 2012 06:58:53 -0400

 (didn't make it to gnats, so included here for background)
 
 On 4/16/12 8:42 PM, Franck PORCHER wrote:
 > The description of the problems is clearly stated from the pr's 
 > description. There should not be any problem with understanding them. 
 > Simply install the stock ports, and start the services just to see 
 > they do not work and understand why from this description.
 >
 > Then the PR comes woith a mix of amended/corected/extended code and 
 > patch-guidelines (no patches proper you can apply with patch) to help 
 > the maintainer test and incorporate them the *way* that suits him best.
 >
 > I'm not strong into patching ports distribution system and do not have 
 > the time right down to delve into it, so to only submit working 
 > patches proper.
 >
 > Nevertheless, I'm very open and willing to discuss both the 
 > description of the problem and my fixes with the maintainer to help 
 > get these fixes mainstream, but only if he/she wishes.
 >
 > For this, feel free to contact me on this email address.
 >
 > With thes fixes, my 2 ports now work perfectly, and it's time they go 
 > mainstream before more users "complain".
 >
 > Cheers,
 >
 > Franck
 >
 
 We do thank you for your time and effort in finding and suggesting some 
 fixes to this( these) ports.  Yes, submitting your first set of ports 
 patches can be daunting, until you do it a couple of times.
 
 Keep in mind that both the maintainer, and FreeBSD ports committers all 
 work on a volunteer basis, and pr's that don't include full patches 
 might take a long time to get worked on.
 
 The maintainer has to try to pull your patches and suggestions out of 
 the attachment you sent, try it locally, and, maybe a lot of back and 
 forth with the pr submitter (you) to make sure they don't mis-understand 
 what you were trying to accomplish.
 
 If you do have some free time, you might want to ask some questions to 
 the freebsd-ports mailing list.  Look at the FreeBSD porters handbook 
 (online)
 
 Depending on what you are doing, as an example:
 
 #########################
 PATCHES
 AND WORK-AROUND
 #########################
 I suggest that a www/py-cherrypy-321 port be temporarily added using CherryPy-3.1.2.tar.gz until the problem with openerp-web.py is solved.
 
 you might add this as a 'BUILD_DEPENDS' or 'RUN_DEPENDS' or both, in the openerp* port Makefile.
 
 if you get to the point where your edited port Makefile works in your environment, you would just submit an attachment with a diff -ruN from the old files to the new onws.
 
 As I said, either that or wait for the maintainer to have the time to sort out what you are doing.
 
 
 
 
 -- 
 Michael Scheidell, CTO
  >*| * SECNAP Network Security Corporation
 d: +1.561.948.2259
 w: http://people.freebsd.org/~scheidell