Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: 76.96.62.32 is neither permitted nor
 denied by domain of dave@brondsema.net)
Message-ID: <501D6DFA.2090009@brondsema.net>
Date: Sat, 04 Aug 2012 14:46:18 -0400
From: Dave Brondsema <dave@brondsema.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: allura-dev@incubator.apache.org
Subject: Re: handling optional GPL dependencies
References: <501C3662.2000308@brondsema.net>
 <CAMRbFx2KzCOgW2BpX1=mwW0fydZ7D+hWb-A9N-2Bmxu8N3oPGQ@mail.gmail.com>
 <501C3AD3.6060309@brondsema.net> <809BB6F4CDB84A329A76616FDF30C6D5@gmail.com>
In-Reply-To: <809BB6F4CDB84A329A76616FDF30C6D5@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 8/3/12 5:01 PM, Wayne Witzel III wrote:
> 
>> Well that's not fun :) I didn't expect we'd have such a big GPL
>> dependency. I don't think we'll want to find or write an alternate
>> Apache library to do the mercurial work, so we may have to split off
>> ForgeHg to somewhere else and not provide it as part of the core Allura.
>>
> That does kind of stink, but fortunately it is very easy in Allura to move that in to its own repo as a separate tool, put it on pypi and add a dependency for it in our requirements.txt. 
> 

Yep, although I think it'd have to be an optional dependency and not in
the default requirements.txt


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><