Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-06-29 Thread David Keller
...@freebsd.org To: Steven Hartland kill...@multiplay.co.uk Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel swhet...@gmail.com; David Keller david.kel...@litchis.fr Sent: Wednesday, April 16, 2014 10:03 AM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 Hi Steven, unfortunately your version

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-06-29 Thread Steven Hartland
; Scot Hetzel swhet...@gmail.com; Sergey A. Osokin o...@freebsd.org Sent: Sunday, June 29, 2014 4:02 PM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 Hi, This should correct the symlink creation error. Regards, David On Wed, Apr 16, 2014 at 5:01 PM, Steven Hartland kill

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-16 Thread Sergey A. Osokin
, April 15, 2014 12:00 AM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 Hi Steven, unfortunately, your patch is wrong and this is why I can't commit your changes. What's wrong in your patch? You have mixed features and bugfixes in one patch. Please provide bugfix only patch

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-16 Thread Steven Hartland
Sent: Wednesday, April 16, 2014 10:03 AM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 Hi Steven, unfortunately your version is different, especially this part of the code: SUB_LIST+= GEM_LIB_DIR=${GEM_LIB_DIR} RUBY=${RUBY} -SUB_FILES= pkg-message +.if ${PORT_OPTIONS:MNGINX

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-15 Thread David Keller
Hello Sergey, Steven's patch already contains the symlink bugfix :-) Regards, David On Tue, Apr 15, 2014 at 12:57 AM, Sergey A. Osokin o...@freebsd.org wrote: Hi David, kindly provide a patch. -- ozz On Sun, Apr 13, 2014 at 12:23:56PM +0200, David Keller wrote: Hi Sergey, It's not

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-14 Thread Sergey A. Osokin
Hi David, kindly provide a patch. -- ozz On Sun, Apr 13, 2014 at 12:23:56PM +0200, David Keller wrote: Hi Sergey, It's not related to gem dependency error but the symlink creation might be incorrect: ${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME} Will create the

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-14 Thread Sergey A. Osokin
Hi Steven, unfortunately, your patch is wrong and this is why I can't commit your changes. What's wrong in your patch? You have mixed features and bugfixes in one patch. Please provide bugfix only patch. -- ozz On Sun, Apr 13, 2014 at 12:28:41PM +0100, Steven Hartland wrote: - Original

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-14 Thread Steven Hartland
: Tuesday, April 15, 2014 12:00 AM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 Hi Steven, unfortunately, your patch is wrong and this is why I can't commit your changes. What's wrong in your patch? You have mixed features and bugfixes in one patch. Please provide bugfix only patch. -- ozz

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-13 Thread David Keller
Hi Sergey, It's not related to gem dependency error but the symlink creation might be incorrect: ${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME} Will create the following symlink: /usr/local/lib/ruby/gems/1.9/gems/passenger - lib/ruby/gems/1.9/gems/passenger-4.0.41 Rather

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-13 Thread Steven Hartland
- Original Message - From: David Keller david.kel...@litchis.fr Hi Sergey, It's not related to gem dependency error but the symlink creation might be incorrect: ${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME} Will create the following symlink:

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-12 Thread Scot Hetzel
On Fri, Apr 11, 2014 at 5:51 PM, Steven Hartland kill...@multiplay.co.uk wrote: The change is from :N - :M .if ${PORT_OPTIONS:MDEBUG} - Select only those words that match DEBUG Which occurs 220 in the port tree and: .if ${PORT_OPTIONS:NDEBUG} - Select words that don't match DEBUG Which

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-12 Thread Sergey A. Osokin
On Sat, Apr 12, 2014 at 03:09:04AM -0500, Scot Hetzel wrote: On Fri, Apr 11, 2014 at 5:51 PM, Steven Hartland kill...@multiplay.co.uk wrote: The change is from :N - :M .if ${PORT_OPTIONS:MDEBUG} - Select only those words that match DEBUG Which occurs 220 in the port tree and: .if

FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread David Keller
Hello, Since rev *350664* (Wed Apr 9 02:36:08 2014 UTC) After *#make install *from */usr/ports/www/rubygem-passenger* /usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41/*buildout* is no longer populated with passenger binaries, hence nginx complains that passenger is not installed.

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread David Keller
PS: building with symlink enabled causes another issue: === Staging for rubygem-passenger-4.0.41_2 === rubygem-passenger-4.0.41_2 depends on executable: nginx - found === rubygem-passenger-4.0.41_2 depends on package: rubygem-fastthread=1.0.1 - found === rubygem-passenger-4.0.41_2

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread Steven Hartland
I've been playing with this and other issues with that port, try the attached patch. Regards Steve - Original Message - From: David Keller david.kel...@litchis.fr To: o...@freebsd.org Cc: po...@freebsd.org Sent: Friday, April 11, 2014 10:29 AM Subject: FreeBSD Port: rubygem

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread David Keller
with that port, try the attached patch. Regards Steve - Original Message - From: David Keller david.kel...@litchis.fr To: o...@freebsd.org Cc: po...@freebsd.org Sent: Friday, April 11, 2014 10:29 AM Subject: FreeBSD Port: rubygem-passenger-4.0.41_2 Hello, Since rev *350664

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread Steven Hartland
- Original Message - From: David Keller david.kel...@litchis.fr It's working :-) But the symlink seems incorrect: * passenger - lib/ruby/gems/1.9/gems/passenger-4.0.41 I might be better like this: * passenger - passenger-4.0.41 Sorry David I've never used the link option, I just

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread Steven Hartland
- Original Message - From: Steven Hartland kill...@multiplay.co.uk To: David Keller david.kel...@litchis.fr Cc: po...@freebsd.org; o...@freebsd.org Sent: Friday, April 11, 2014 12:04 PM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 - Original Message - From: David

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread David Keller
: Steven Hartland kill...@multiplay.co.uk To: David Keller david.kel...@litchis.fr Cc: po...@freebsd.org; o...@freebsd.org Sent: Friday, April 11, 2014 12:04 PM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 - Original Message - From: David Keller david.kel...@litchis.fr

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread Sergey A. Osokin
: David Keller david.kel...@litchis.fr To: o...@freebsd.org Cc: po...@freebsd.org Sent: Friday, April 11, 2014 10:29 AM Subject: FreeBSD Port: rubygem-passenger-4.0.41_2 Hello, Since rev *350664* (Wed Apr 9 02:36:08 2014 UTC) After *#make install *from */usr/ports/www/rubygem

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

2014-04-11 Thread Steven Hartland
...@multiplay.co.uk Cc: David Keller david.kel...@litchis.fr; po...@freebsd.org Sent: Friday, April 11, 2014 11:27 PM Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2 Hi Steven, looks good, except one thing: -.if ${PORT_OPTIONS:NDEBUG} +.if ${PORT_OPTIONS:MDEBUG} Could you explain what's