On Jan 28, 2012, at 20:22 , Philip M. Gollucci wrote:
> On 1/28/12 1:52 AM, Tilman Keskinöz wrote:
>> If there is no reason, the port should be either fixed, or the commit backed
>> out!
> This is not a unique problem among gems. Lots of them screw up umasks on
> install. Some too restrictive
On 1/28/12 1:52 AM, Tilman Keskinöz wrote:
If there is no reason, the port should be either fixed, or the commit backed
out!
This is not a unique problem among gems. Lots of them screw up umasks
on install. Some too restrictive, some overly lax.
--
-
If there is no reason, the port should be either fixed, or the commit backed
out!
On Jan 27, 2012, at 18:39 , Philip M. Gollucci wrote:
> You'd have to ask the gem author. Nothing is jumping out at me in the code.
>
>
>
> On 01/27/12 15:35, Tilman Keskinöz wrote:
>> * Philip M. Gollucci [Tue
You'd have to ask the gem author. Nothing is jumping out at me in the code.
On 01/27/12 15:35, Tilman Keskinöz wrote:
> * Philip M. Gollucci [Tue, 20 Dec 2011 05:11:02 + (UTC)]:
>> pgollucci2011-12-20 05:10:43 UTC
>>
>> FreeBSD ports repository
>>
>> Modified files:
>> devel/rub
* Philip M. Gollucci [Tue, 20 Dec 2011 05:11:02 + (UTC)]:
> pgollucci2011-12-20 05:10:43 UTC
>
> FreeBSD ports repository
>
> Modified files:
> devel/rubygem-daemons Makefile distinfo
> Log:
> - Update to 1.1.5
>
> With Hat: ruby@
> Sponsored by: RideCharge Inc
