Virtualenv is not a hard requirement but is convenient. I believe that
we already have instructions that point out that activating a virtualenv
is optional. I think we will just have to present this information to
OSX users to allow them to make their own choice.
If we can avoid wasting time in creating a full installer, this would be
a very good thing. I believe that we are doing enough by providing
appropriate instructions for successful installation and good basic
initial configuration.
Cheers,
Gary
On 09/19/2012 03:03 PM, John Chambers wrote:
If using virtualenv is a hard requirement for the basic running of
Bloodhound then we just need to document, that on OSX we have a dependancy
on the xcode command line tools. Unless we can find a way around this. I am
neither an expert on OSX or python (yet).
As for the wide issue of providing installer packages I agree with Ian that
these are normally provided outside of the main project along with
providing support and other ancillary services. But we still need to
provide the instruction to get Bloodhound up and running as quickly and
easily as possible, with the least impact on the users existing system.
