Sergey,
Romain Tartière (romain@) has just commented at
https://reviews.freebsd.org/D13889:
"Great, this has annoyed me for a while, I fixed this upstream but this has not
been released yet. Patching will therefore become useless in the future, but
for now, thanks for fixing this!"
Given the
Hello Sergey,
The proposed solution is a short term solution which goes away when FLAVORS are
done for ruby. This is not soon.
We (feld@ & I) choose this solution as it has very little affect on the
existing port.
The need arose today & we hope to proceed quickly with whatever can be done.
> On Jan 12, 2018, at 11:48 AM, Dan Langille wrote:
>
>
>> On Fri, Jan 12, 2018 at 7:23 AM, Dan Langille wrote:
>>> On Jan 12, 2018, at 10:18 AM, Dan Langille wrote:
>>>
>>> Sergey,
>>>
>>> We have a need to use rubygem-passenger with
> On Fri, Jan 12, 2018 at 7:23 AM, Dan Langille wrote:
> > On Jan 12, 2018, at 10:18 AM, Dan Langille wrote:
> >
> > Sergey,
> >
> > We have a need to use rubygem-passenger with both Nginx and with Apache (on
> > different servers).
> >
> > I propose to
This is an example of a perfect use case for flavors. Instead of
a slave port, creating an nginx flavor and apache flavor would
be a better approach.
Best regards,
Richard Gallamore
On Fri, Jan 12, 2018 at 7:23 AM, Dan Langille wrote:
> > On Jan 12, 2018, at 10:18 AM, Dan
> On Jan 12, 2018, at 10:18 AM, Dan Langille wrote:
>
> Sergey,
>
> We have a need to use rubygem-passenger with both Nginx and with Apache (on
> different servers).
>
> I propose to create two new slave ports:
>
> * www/rubygem-passenger-nginx
> *
Sergey,
We have a need to use rubygem-passenger with both Nginx and with Apache (on
different servers).
I propose to create two new slave ports:
* www/rubygem-passenger-nginx
* www/rubygem-passenger-passenger
To do this, I would like to make a one-line change to the master port:
Index: