You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gary <ga...@wandisco.com> on 2012/03/05 17:17:30 UTC
Re: svn commit: r1297104 - in /incubator/bloodhound/trunk/installer:
./ LICENSE NOTICE README.rst createdigest.py installer.py pgrequirements.txt
requirements.txt
Hi everyone,
I just thought that with this commit I would let you know that I have
written an installer of sorts. It definitely needs more testing (I have
stuck with Ubuntu 11.10 for this initial work) but it might serve as a
reasonable starting point to get people able to be more involved, at
least in the short term.
At the moment it will install the trac dependency from
https://svn.github.com/bloodhound-trac/trac.git (so through github's svn
translation layer). The only plugins that are installed at the moment
are TracAccountManager and BloodhoundMultiProduct. The latter will
modify an existing Trac database if it is told how to connect to it and
so it is not recommended to install this against a production system.
The README.rst contains some description of how it can be used and this
too could do with checking for accuracy or missed details.
Cheers,
Gary
On 03/05/2012 03:57 PM, gjm@apache.org wrote:
> Author: gjm
> Date: Mon Mar 5 15:57:00 2012
> New Revision: 1297104
>
> URL: http://svn.apache.org/viewvc?rev=1297104&view=rev
> Log:
> very basic candidate bloodhound installer
>
> Added:
> incubator/bloodhound/trunk/installer/
> incubator/bloodhound/trunk/installer/LICENSE (with props)
> incubator/bloodhound/trunk/installer/NOTICE (with props)
> incubator/bloodhound/trunk/installer/README.rst (with props)
> incubator/bloodhound/trunk/installer/createdigest.py (with props)
> incubator/bloodhound/trunk/installer/installer.py (with props)
> incubator/bloodhound/trunk/installer/pgrequirements.txt (with props)
> incubator/bloodhound/trunk/installer/requirements.txt (with props)
> [snip]
Re: Getting involved and installation pages
Posted by Joachim Dreimann <jo...@wandisco.com>.
I have now also added a section on how to get involved in the
UI/Design process (other than code as such).
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing#ContributingDesigns
Any feedback appreciated.
- Joe
On 13 March 2012 11:08, Gary <ga...@wandisco.com> wrote:
> Hi,
>
> Just changed the installer to supply a logger object for virtualenv when it
> is missing.
>
> Cheers,
> Gary
>
>
> On 03/13/2012 10:55 AM, gjm@apache.org wrote:
>>
>> Author: gjm
>> Date: Tue Mar 13 10:55:14 2012
>> New Revision: 1300071
>>
>> URL: http://svn.apache.org/viewvc?rev=1300071&view=rev
>> Log:
>> maintain compatibility with older versions of virtualenv, fixing #4
>>
>> Modified:
>> incubator/bloodhound/trunk/installer/installer.py
>
>
> On 03/12/2012 10:25 AM, Gary wrote:
>>
>> Hi Antony,
>>
>> Thanks for that.
>>
>> OK, I would prefer not to have to specify a minimum version of virtualenv
>> that is newer than that available for the default version of a major linux
>> distribution. So we can either resort to calling virtualenv through
>> subprocess or we can do to the following:
>>
>> if not hasattr(virtualenv, 'logger'):
>> virtualenv.logger =
>> virtualenv.Logger([(virtualenv.Logger.LEVELS[-1],
>> sys.stdout)])
>>
>>
>> Cheers,
>> Gary
>>
>>
>> On 03/10/2012 12:36 PM, Antony Semonella wrote:
>>>
>>> Hello,
>>>
>>> I managed to set up a bloodhound development environment on Debian 6.0
>>> following the instructions at:
>>>
>>> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>>>
>>> You may want to update the wiki to highlight the following dependency I
>>> encountered:
>>>
>>> The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3;
>>> this
>>> version of virtualenv results in:
>>>
>>> NameError: global name 'logger' is not defined
>>>
>>> When running bloodhound/installer/installer.py.
>>>
>>> logger is defined only in main() for this version of virtualenv.
>>>
>>> This issue has been resolved by:
>>>
>>> https://github.com/pypa/virtualenv/commit/ea1786
>>>
>>> Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
>>> and so the bloodhound dev. environment was setup ok for me.
>>>
>>> I therefore suggest a version of virtualenv>=1.7.1.2 be listed as a
>>> dependency.
>>>
>>> Cheers!
>>>
>>> Antony
>
>
Re: Getting involved and installation pages
Posted by Gary <ga...@wandisco.com>.
Hi,
Just changed the installer to supply a logger object for virtualenv when
it is missing.
Cheers,
Gary
On 03/13/2012 10:55 AM, gjm@apache.org wrote:
> Author: gjm
> Date: Tue Mar 13 10:55:14 2012
> New Revision: 1300071
>
> URL: http://svn.apache.org/viewvc?rev=1300071&view=rev
> Log:
> maintain compatibility with older versions of virtualenv, fixing #4
>
> Modified:
> incubator/bloodhound/trunk/installer/installer.py
On 03/12/2012 10:25 AM, Gary wrote:
> Hi Antony,
>
> Thanks for that.
>
> OK, I would prefer not to have to specify a minimum version of
> virtualenv that is newer than that available for the default version
> of a major linux distribution. So we can either resort to calling
> virtualenv through subprocess or we can do to the following:
>
> if not hasattr(virtualenv, 'logger'):
> virtualenv.logger =
> virtualenv.Logger([(virtualenv.Logger.LEVELS[-1],
> sys.stdout)])
>
>
> Cheers,
> Gary
>
>
> On 03/10/2012 12:36 PM, Antony Semonella wrote:
>> Hello,
>>
>> I managed to set up a bloodhound development environment on Debian 6.0
>> following the instructions at:
>>
>> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>>
>> You may want to update the wiki to highlight the following dependency I
>> encountered:
>>
>> The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3; this
>> version of virtualenv results in:
>>
>> NameError: global name 'logger' is not defined
>>
>> When running bloodhound/installer/installer.py.
>>
>> logger is defined only in main() for this version of virtualenv.
>>
>> This issue has been resolved by:
>>
>> https://github.com/pypa/virtualenv/commit/ea1786
>>
>> Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
>> and so the bloodhound dev. environment was setup ok for me.
>>
>> I therefore suggest a version of virtualenv>=1.7.1.2 be listed as a
>> dependency.
>>
>> Cheers!
>>
>> Antony
Re: Getting involved and installation pages
Posted by Gary <ga...@wandisco.com>.
Hi Antony,
Thanks for that.
OK, I would prefer not to have to specify a minimum version of
virtualenv that is newer than that available for the default version of
a major linux distribution. So we can either resort to calling
virtualenv through subprocess or we can do to the following:
if not hasattr(virtualenv, 'logger'):
virtualenv.logger =
virtualenv.Logger([(virtualenv.Logger.LEVELS[-1],
sys.stdout)])
Cheers,
Gary
On 03/10/2012 12:36 PM, Antony Semonella wrote:
> Hello,
>
> I managed to set up a bloodhound development environment on Debian 6.0
> following the instructions at:
>
> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>
> You may want to update the wiki to highlight the following dependency I
> encountered:
>
> The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3; this
> version of virtualenv results in:
>
> NameError: global name 'logger' is not defined
>
> When running bloodhound/installer/installer.py.
>
> logger is defined only in main() for this version of virtualenv.
>
> This issue has been resolved by:
>
> https://github.com/pypa/virtualenv/commit/ea1786
>
> Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
> and so the bloodhound dev. environment was setup ok for me.
>
> I therefore suggest a version of virtualenv>=1.7.1.2 be listed as a
> dependency.
>
> Cheers!
>
> Antony
>
>
>
> On 9 March 2012 14:48, Antony Semonella<as...@gmail.com> wrote:
>
>> Cool, I'll give the docs a read (as a newcomer) and provide some feedback
>> :)
>>
>>
>> On 9 March 2012 14:35, Gary<ga...@wandisco.com> wrote:
>>
>>> Hi everyone,
>>>
>>> We now have https://issues.apache.org/**bloodhound/wiki/**
>>> BloodhoundContributing<https://issues.apache.org/bloodhound/wiki/BloodhoundContributing>
>>>
>>> As always, this definitely needs some expanding upon and improving but I
>>> hope it can serve as a reasonable starting point - we definitely need to
>>> discuss other ways of helping like contributing to documentation and
>>> reporting bugs. And there are definitely a lot of documentation tasks to be
>>> done as we get new features in.
>>>
>>> Cheers,
>>> Gary
>>>
>>>
>>> On 03/08/2012 06:00 PM, Antony Semonella wrote:
>>>
>>>> That sounds great.
>>>>
>>>> Cheers,
>>>>
>>>> Antony
>>>>
>>>> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>>>>
>>>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>>>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>>>>> to codify these kinds of steps into something we can point newcomers
>>>>>> to.
>>>>>>
>>>>>> -Hyrum
>>>>>>
>>>>>> Good idea.
>>>>> Meanwhile I have added a few pages relating to installation to the wiki
>>>>> at:
>>>>> * https://issues.apache.org/****bloodhound/wiki/****BloodhoundInstall<https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall>
>>>>> <https://**issues.apache.org/bloodhound/**wiki/BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>>>>> * https://issues.apache.org/****bloodhound/wiki/**<https://issues.apache.org/**bloodhound/wiki/**>
>>>>> BloodhoundDetailedInstallation**<https://issues.apache.org/**
>>>>> bloodhound/wiki/**BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>>>> **>
>>>>>
>>>>>
>>>>> I will look at writing something about getting involved very soon unless
>>>>> someone else wants to look at that.
>>>>>
>>>>> Cheers,
>>>>> Gary
>>>>>
>>>>>
>>>>>
Re: Getting involved and installation pages
Posted by Antony Semonella <as...@gmail.com>.
Hello,
I managed to set up a bloodhound development environment on Debian 6.0
following the instructions at:
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
You may want to update the wiki to highlight the following dependency I
encountered:
The version of virtualenv in the repo for Debian squeeze is: 1.4.9-3; this
version of virtualenv results in:
NameError: global name 'logger' is not defined
When running bloodhound/installer/installer.py.
logger is defined only in main() for this version of virtualenv.
This issue has been resolved by:
https://github.com/pypa/virtualenv/commit/ea1786
Using the latest version of virtualenv (1.7.1.2) resulted in no NameError
and so the bloodhound dev. environment was setup ok for me.
I therefore suggest a version of virtualenv >=1.7.1.2 be listed as a
dependency.
Cheers!
Antony
On 9 March 2012 14:48, Antony Semonella <as...@gmail.com> wrote:
> Cool, I'll give the docs a read (as a newcomer) and provide some feedback
> :)
>
>
> On 9 March 2012 14:35, Gary <ga...@wandisco.com> wrote:
>
>> Hi everyone,
>>
>> We now have https://issues.apache.org/**bloodhound/wiki/**
>> BloodhoundContributing<https://issues.apache.org/bloodhound/wiki/BloodhoundContributing>
>>
>> As always, this definitely needs some expanding upon and improving but I
>> hope it can serve as a reasonable starting point - we definitely need to
>> discuss other ways of helping like contributing to documentation and
>> reporting bugs. And there are definitely a lot of documentation tasks to be
>> done as we get new features in.
>>
>> Cheers,
>> Gary
>>
>>
>> On 03/08/2012 06:00 PM, Antony Semonella wrote:
>>
>>> That sounds great.
>>>
>>> Cheers,
>>>
>>> Antony
>>>
>>> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>>>
>>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>>>
>>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>>>> to codify these kinds of steps into something we can point newcomers
>>>>> to.
>>>>>
>>>>> -Hyrum
>>>>>
>>>>> Good idea.
>>>>
>>>> Meanwhile I have added a few pages relating to installation to the wiki
>>>> at:
>>>> * https://issues.apache.org/****bloodhound/wiki/****BloodhoundInstall<https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall>
>>>> <https://**issues.apache.org/bloodhound/**wiki/BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>>>> >
>>>> * https://issues.apache.org/****bloodhound/wiki/**<https://issues.apache.org/**bloodhound/wiki/**>
>>>> BloodhoundDetailedInstallation**<https://issues.apache.org/**
>>>> bloodhound/wiki/**BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>>> **>
>>>>
>>>>
>>>> I will look at writing something about getting involved very soon unless
>>>> someone else wants to look at that.
>>>>
>>>> Cheers,
>>>> Gary
>>>>
>>>>
>>>>
>>
>
Re: Getting involved and installation pages
Posted by Antony Semonella <as...@gmail.com>.
Cool, I'll give the docs a read (as a newcomer) and provide some feedback :)
On 9 March 2012 14:35, Gary <ga...@wandisco.com> wrote:
> Hi everyone,
>
> We now have https://issues.apache.org/**bloodhound/wiki/**
> BloodhoundContributing<https://issues.apache.org/bloodhound/wiki/BloodhoundContributing>
>
> As always, this definitely needs some expanding upon and improving but I
> hope it can serve as a reasonable starting point - we definitely need to
> discuss other ways of helping like contributing to documentation and
> reporting bugs. And there are definitely a lot of documentation tasks to be
> done as we get new features in.
>
> Cheers,
> Gary
>
>
> On 03/08/2012 06:00 PM, Antony Semonella wrote:
>
>> That sounds great.
>>
>> Cheers,
>>
>> Antony
>>
>> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>>
>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>>
>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>>> to codify these kinds of steps into something we can point newcomers
>>>> to.
>>>>
>>>> -Hyrum
>>>>
>>>> Good idea.
>>>
>>> Meanwhile I have added a few pages relating to installation to the wiki
>>> at:
>>> * https://issues.apache.org/****bloodhound/wiki/****BloodhoundInstall<https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall>
>>> <https://**issues.apache.org/bloodhound/**wiki/BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>>> >
>>> * https://issues.apache.org/****bloodhound/wiki/**<https://issues.apache.org/**bloodhound/wiki/**>
>>> BloodhoundDetailedInstallation**<https://issues.apache.org/**
>>> bloodhound/wiki/**BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>> **>
>>>
>>>
>>> I will look at writing something about getting involved very soon unless
>>> someone else wants to look at that.
>>>
>>> Cheers,
>>> Gary
>>>
>>>
>>>
>
Re: Getting involved and installation pages
Posted by Gary <ga...@wandisco.com>.
Hi everyone,
We now have https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
As always, this definitely needs some expanding upon and improving but I
hope it can serve as a reasonable starting point - we definitely need to
discuss other ways of helping like contributing to documentation and
reporting bugs. And there are definitely a lot of documentation tasks to
be done as we get new features in.
Cheers,
Gary
On 03/08/2012 06:00 PM, Antony Semonella wrote:
> That sounds great.
>
> Cheers,
>
> Antony
>
> On 8 March 2012 17:36, Gary<ga...@wandisco.com> wrote:
>
>> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>>
>>> Out of curiosity, do we have a "how to get involved" or "beginner's
>>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>>> to codify these kinds of steps into something we can point newcomers
>>> to.
>>>
>>> -Hyrum
>>>
>> Good idea.
>>
>> Meanwhile I have added a few pages relating to installation to the wiki at:
>> * https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
>> * https://issues.apache.org/**bloodhound/wiki/**
>> BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>>
>> I will look at writing something about getting involved very soon unless
>> someone else wants to look at that.
>>
>> Cheers,
>> Gary
>>
>>
Re: Getting involved and installation pages
Posted by Antony Semonella <as...@gmail.com>.
That sounds great.
Cheers,
Antony
On 8 March 2012 17:36, Gary <ga...@wandisco.com> wrote:
> On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
>
>> Out of curiosity, do we have a "how to get involved" or "beginner's
>> guide to Bloodhound" wiki page or document anywhere? It'd be useful
>> to codify these kinds of steps into something we can point newcomers
>> to.
>>
>> -Hyrum
>>
>
> Good idea.
>
> Meanwhile I have added a few pages relating to installation to the wiki at:
> * https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall<https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>
> * https://issues.apache.org/**bloodhound/wiki/**
> BloodhoundDetailedInstallation<https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation>
>
> I will look at writing something about getting involved very soon unless
> someone else wants to look at that.
>
> Cheers,
> Gary
>
>
Getting involved and installation pages
Posted by Gary <ga...@wandisco.com>.
On 03/07/2012 05:23 PM, Hyrum K Wright wrote:
> Out of curiosity, do we have a "how to get involved" or "beginner's
> guide to Bloodhound" wiki page or document anywhere? It'd be useful
> to codify these kinds of steps into something we can point newcomers
> to.
>
> -Hyrum
Good idea.
Meanwhile I have added a few pages relating to installation to the wiki at:
* https://issues.apache.org/bloodhound/wiki/BloodhoundInstall
* https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation
I will look at writing something about getting involved very soon unless
someone else wants to look at that.
Cheers,
Gary
Re: svn commit: r1297104 - in /incubator/bloodhound/trunk/installer:
./ LICENSE NOTICE README.rst createdigest.py installer.py pgrequirements.txt requirements.txt
Posted by Hyrum K Wright <hy...@wandisco.com>.
Out of curiosity, do we have a "how to get involved" or "beginner's
guide to Bloodhound" wiki page or document anywhere? It'd be useful
to codify these kinds of steps into something we can point newcomers
to.
-Hyrum
On Wed, Mar 7, 2012 at 11:09 AM, Gary <ga...@wandisco.com> wrote:
> Hi Antony,
>
> I'm glad I was able to convince you that it is an interesting project..
>
> Any help you think you can offer would be fantastic. Thanks!
>
> Cheers,
> Gary
>
>
>
> On 03/07/2012 04:34 PM, Antony Semonella wrote:
>>
>> Hello there,
>>
>> I'm interested in bug-fixing. I've been using Python professionally for
>> the
>> past 5 years
>> and have been using Trac on a daily basis for the same length of time.
>>
>> Bloodhound seems an interesting project.
>>
>> Cheers,
>>
>> Antony
>>
>> On 5 March 2012 16:17, Gary<ga...@wandisco.com> wrote:
>>
>>> Hi everyone,
>>>
>>> I just thought that with this commit I would let you know that I have
>>> written an installer of sorts. It definitely needs more testing (I have
>>> stuck with Ubuntu 11.10 for this initial work) but it might serve as a
>>> reasonable starting point to get people able to be more involved, at
>>> least
>>> in the short term.
>>>
>>> At the moment it will install the trac dependency from
>>>
>>> https://svn.github.com/**bloodhound-trac/trac.git<https://svn.github.com/bloodhound-trac/trac.git>(so
>>> through github's svn translation layer). The only plugins that are
>>> installed at the moment are TracAccountManager and
>>> BloodhoundMultiProduct.
>>> The latter will modify an existing Trac database if it is told how to
>>> connect to it and so it is not recommended to install this against a
>>> production system.
>>>
>>> The README.rst contains some description of how it can be used and this
>>> too could do with checking for accuracy or missed details.
>>>
>>> Cheers,
>>> Gary
>>>
>>>
>>> On 03/05/2012 03:57 PM, gjm@apache.org wrote:
>>>
>>>> Author: gjm
>>>> Date: Mon Mar 5 15:57:00 2012
>>>> New Revision: 1297104
>>>>
>>>> URL:
>>>> http://svn.apache.org/viewvc?**rev=1297104&view=rev<http://svn.apache.org/viewvc?rev=1297104&view=rev>
>>>> Log:
>>>> very basic candidate bloodhound installer
>>>>
>>>> Added:
>>>> incubator/bloodhound/trunk/**installer/
>>>> incubator/bloodhound/trunk/**installer/LICENSE (with props)
>>>> incubator/bloodhound/trunk/**installer/NOTICE (with props)
>>>> incubator/bloodhound/trunk/**installer/README.rst (with props)
>>>> incubator/bloodhound/trunk/**installer/createdigest.py (with
>>>> props)
>>>> incubator/bloodhound/trunk/**installer/installer.py (with props)
>>>> incubator/bloodhound/trunk/**installer/pgrequirements.txt (with
>>>> props)
>>>> incubator/bloodhound/trunk/**installer/requirements.txt (with
>>>> props)
>>>> [snip]
>>>>
>>>
>
--
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com/
Re: svn commit: r1297104 - in /incubator/bloodhound/trunk/installer:
./ LICENSE NOTICE README.rst createdigest.py installer.py pgrequirements.txt
requirements.txt
Posted by Gary <ga...@wandisco.com>.
Hi Antony,
I'm glad I was able to convince you that it is an interesting project..
Any help you think you can offer would be fantastic. Thanks!
Cheers,
Gary
On 03/07/2012 04:34 PM, Antony Semonella wrote:
> Hello there,
>
> I'm interested in bug-fixing. I've been using Python professionally for the
> past 5 years
> and have been using Trac on a daily basis for the same length of time.
>
> Bloodhound seems an interesting project.
>
> Cheers,
>
> Antony
>
> On 5 March 2012 16:17, Gary<ga...@wandisco.com> wrote:
>
>> Hi everyone,
>>
>> I just thought that with this commit I would let you know that I have
>> written an installer of sorts. It definitely needs more testing (I have
>> stuck with Ubuntu 11.10 for this initial work) but it might serve as a
>> reasonable starting point to get people able to be more involved, at least
>> in the short term.
>>
>> At the moment it will install the trac dependency from
>> https://svn.github.com/**bloodhound-trac/trac.git<https://svn.github.com/bloodhound-trac/trac.git>(so through github's svn translation layer). The only plugins that are
>> installed at the moment are TracAccountManager and BloodhoundMultiProduct.
>> The latter will modify an existing Trac database if it is told how to
>> connect to it and so it is not recommended to install this against a
>> production system.
>>
>> The README.rst contains some description of how it can be used and this
>> too could do with checking for accuracy or missed details.
>>
>> Cheers,
>> Gary
>>
>>
>> On 03/05/2012 03:57 PM, gjm@apache.org wrote:
>>
>>> Author: gjm
>>> Date: Mon Mar 5 15:57:00 2012
>>> New Revision: 1297104
>>>
>>> URL: http://svn.apache.org/viewvc?**rev=1297104&view=rev<http://svn.apache.org/viewvc?rev=1297104&view=rev>
>>> Log:
>>> very basic candidate bloodhound installer
>>>
>>> Added:
>>> incubator/bloodhound/trunk/**installer/
>>> incubator/bloodhound/trunk/**installer/LICENSE (with props)
>>> incubator/bloodhound/trunk/**installer/NOTICE (with props)
>>> incubator/bloodhound/trunk/**installer/README.rst (with props)
>>> incubator/bloodhound/trunk/**installer/createdigest.py (with props)
>>> incubator/bloodhound/trunk/**installer/installer.py (with props)
>>> incubator/bloodhound/trunk/**installer/pgrequirements.txt (with
>>> props)
>>> incubator/bloodhound/trunk/**installer/requirements.txt (with
>>> props)
>>> [snip]
>>>
>>
Re: svn commit: r1297104 - in /incubator/bloodhound/trunk/installer:
./ LICENSE NOTICE README.rst createdigest.py installer.py pgrequirements.txt requirements.txt
Posted by Antony Semonella <as...@gmail.com>.
Hello there,
I'm interested in bug-fixing. I've been using Python professionally for the
past 5 years
and have been using Trac on a daily basis for the same length of time.
Bloodhound seems an interesting project.
Cheers,
Antony
On 5 March 2012 16:17, Gary <ga...@wandisco.com> wrote:
> Hi everyone,
>
> I just thought that with this commit I would let you know that I have
> written an installer of sorts. It definitely needs more testing (I have
> stuck with Ubuntu 11.10 for this initial work) but it might serve as a
> reasonable starting point to get people able to be more involved, at least
> in the short term.
>
> At the moment it will install the trac dependency from
> https://svn.github.com/**bloodhound-trac/trac.git<https://svn.github.com/bloodhound-trac/trac.git>(so through github's svn translation layer). The only plugins that are
> installed at the moment are TracAccountManager and BloodhoundMultiProduct.
> The latter will modify an existing Trac database if it is told how to
> connect to it and so it is not recommended to install this against a
> production system.
>
> The README.rst contains some description of how it can be used and this
> too could do with checking for accuracy or missed details.
>
> Cheers,
> Gary
>
>
> On 03/05/2012 03:57 PM, gjm@apache.org wrote:
>
>> Author: gjm
>> Date: Mon Mar 5 15:57:00 2012
>> New Revision: 1297104
>>
>> URL: http://svn.apache.org/viewvc?**rev=1297104&view=rev<http://svn.apache.org/viewvc?rev=1297104&view=rev>
>> Log:
>> very basic candidate bloodhound installer
>>
>> Added:
>> incubator/bloodhound/trunk/**installer/
>> incubator/bloodhound/trunk/**installer/LICENSE (with props)
>> incubator/bloodhound/trunk/**installer/NOTICE (with props)
>> incubator/bloodhound/trunk/**installer/README.rst (with props)
>> incubator/bloodhound/trunk/**installer/createdigest.py (with props)
>> incubator/bloodhound/trunk/**installer/installer.py (with props)
>> incubator/bloodhound/trunk/**installer/pgrequirements.txt (with
>> props)
>> incubator/bloodhound/trunk/**installer/requirements.txt (with
>> props)
>> [snip]
>>
>
>
Re: svn commit: r1297104 - in /incubator/bloodhound/trunk/installer:
./ LICENSE NOTICE README.rst createdigest.py installer.py pgrequirements.txt requirements.txt
Posted by Olemis Lang <ol...@gmail.com>.
I repeat ...
:-/
On Wed, Mar 7, 2012 at 7:39 AM, Olemis Lang <ol...@gmail.com> wrote:
> On Mon, Mar 5, 2012 at 11:17 AM, Gary <ga...@wandisco.com> wrote:
>>
[...]
>> I just thought that with this commit I would let you know that I have written an installer of sorts. It definitely needs more testing (I have stuck with Ubuntu 11.10 for this initial work) but it might serve as a reasonable starting point to get people able to be more involved, at least in the short term.
>>
>>
>
My only suggestion here is to provide a separate function so as to
populate options parser and reuse it inside main . The reason for
doing this is to ease the task of writing more complex (Python)
scripts by embedding Bloodhound installer rather than invoking it as
an external script , i.e. something like this :
{{{
#!py
def custom_installer():
parser = OptionParser(*args)
add_bloodhound_options(parser)
add_someother_options(parser)
options, args = parser.parse_options()
install_result = install_bloodhound(options, args) #
<= this one will be `main`
install_result = install_yetanother_app_or_plugin(options, args)
return install_result
}}}
... this may be useful
;)
--
Regards,
Olemis.
Re: svn commit: r1297104 - in /incubator/bloodhound/trunk/installer:
./ LICENSE NOTICE README.rst createdigest.py installer.py pgrequirements.txt requirements.txt
Posted by Olemis Lang <ol...@gmail.com>.
On Mon, Mar 5, 2012 at 11:17 AM, Gary <ga...@wandisco.com> wrote:
>
> Hi everyone,
>
:)
>
> I just thought that with this commit I would let you know that I have written an installer of sorts. It definitely needs more testing (I have stuck with Ubuntu 11.10 for this initial work) but it might serve as a reasonable starting point to get people able to be more involved, at least in the short term.
>
>
My only suggestion here is to provide a separate function so as to
populate options parser and reuse it inside main . The reason for
doing this is to ease the task of writing more complex (Python)
scripts by embedding Bloodhound installer rather than invoking it from
the CLI i.e. sometho
[...]
--
Regards,
Olemis.