mini-Summit report, day 2

Daira Hopwood daira at jacaranda.org
Tue Jul 29 21:35:30 UTC 2014


On 02/07/14 22:50, Greg Troxel wrote:
> 
> Brian Warner <warner at lothar.com> writes:
> 
>> Summary of the second day. Brian, Daira, and Nathan met in a coffee
>> shop, and we:
>>
>> * built a branch that replaces Tahoe's build process with the "create a
>>   virtualenv, peep-install everything into it, make bin/tahoe run
>>   venv/bin/tahoe" technique that Brian used in Petmail. Modulo
>>   bugs/limitations in Peep, this is "safe", in that it checks
>>   pre-specified hashes on all tarballs before running any code from
>>   them. If you managed to get a "good" copy of tahoe's source code, this
>>   would ensure that you only use "good" code for tahoe's dependencies.
> 
> Hopefully this has a way to avoid doing any fetching of dependencies,
> and failing instead,

Yes, fetching dependencies and building will be separate steps when this is
finished.

> and is no less cross unfriendly than python has to be to start with.

It would be up to virtualenv to support creating a cross-build environment.
It's possible in theory; see
<http://whatschrisdoing.com/blog/2009/10/16/cross-compiling-python-extensions/>

> (From packaging system view)   tahoe really doesn't
> seem all that special - it's just a bunch of python code with a list of
> dependencies, so it seems symptomatic of larger brokenness in the python
> world that this is necessary...

Yes, of course. But that world is *very* broken, especially for packages
with C dependencies.

-- 
Daira Hopwood ⚥

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20140729/7a7b6e51/attachment.pgp>


More information about the tahoe-dev mailing list