[Chandler-dev] Chandler new-version detection

[Phillip J. Eby]

At 05:16 PM 11/21/2007 -0500, Mike Taylor wrote:

>On Nov 21, 2007, at 2:02 PM, Phillip J. Eby wrote:
>
>>At 09:41 AM 11/21/2007 -0800, Heikki Toivonen wrote:
>>>Morgen Sagen wrote:
>>> > Under the hood it uses urllib, which we can configure to honor
>>>whatever
>>> > proxy settings the user has entered in Chandler.  Heikki
>>>mentioned a
>>> > desire to use HTTPS which means we would need proxy support for
>>>HTTPS as
>>> > well.
>>> >
>>> > What do people think about using setuptools for new-version
>>>detection?
>>>
>>>In principle that sounds great; I am not keen on reinventing either.
>>>
>>>Would this require putting something on cheeseshop for setuptools to
>>>detect a new Chandler version, or can you tell setuptools where to
>>>look?
>>
>>The PackageIndex.find_links(url_list) method will give it specific
>>URLs; these can be any HTML web page, as long as they contain links
>>to directly-downloadable eggs or other easy_install-able
>>distribution formats.  It can also be given a host mask to restrict
>>what hosts it will attempt to connect to (either to read HTML or
>>download other files).
>
>This would be a good reason to have our own PyPI repository to act as
>the primary for "official" upgrades and to act as a backup to the
>normal one for plugins and the like.

You don't need a "repository" for that; just make a single web page 
with all the available downloads on it.  An Apache DirectoryIndex of 
a directory with all the files dumped in it is sufficient.

Users then specify the URL of that directory in a -f option to 
easy_install, or of course our own tools can include it 
automatically.  The PackageIndex class already checks such pages 
before going to PyPI.