incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko Čibej <br...@wandisco.com>
Subject Re: Unable to install bloodhound from svn, pip install fails
Date Thu, 23 Aug 2012 07:55:24 GMT
On 23.08.2012 01:55, Olemis Lang wrote:
> On 8/22/12, Branko Čibej <brane@wandisco.com> wrote:
>> On 22.08.2012 19:32, Gary Martin wrote:
>>> On 08/22/2012 05:36 PM, Olemis Lang wrote:
>>>>    - TracPermRedirect is not hosted in PyPI
>>> Looks like it is there to me.
>>>
> Oops !
> I coudn't find it ...
> :'(
>
> [...]
>>>> IMO we should have a small package index (in ASF repository ?) in
>>>> order to provide alternate download links (e.g. PyPI , Bitbucket ,
>>>> ...) to handle situations like this .
>>> A local ASF cheeseshop might be interesting, although I don't know
>>> whether it is something that would be difficult to argue for.
>> Given the ASF policy for releasing source, not binary packages, it's not
>> very likely to happen.
> Hmmm ... It seems everything I said was not understood the way I
> wanted to. So I'll try to explain myself better . I was talking about
> creating somewhere (ASF repos, file attached to wiki, or somewhere
> else) an index listing candidate files for downloading plugins. Just
> that . Links would point to external website (e.g. t-h.o) just in a
> way similar to requirements files including t-h.o URLs nowadays . The
> benefit of using index file over requirements spec is mainly that it'd
> be possible to state e.g. «try to download ThemeEngine from t-h.o
> otherwise consider PyPI, else try unofficial Bitbucket repository,
> ...» . The index limited to the plugins we need to run Bloodhound . In
> order to do so , afaics we could track versions of those index files
> in ASF repos , isn't it ?

Yes, that's OK. Sorry I misunderstood your intent.

-- Brane


-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download


Mime
View raw message