Ludovic Courtès writes:
>> I could only coerce the build system to install plain files by adding a
>> build phase like this:
>>
>> (add-after 'unpack 'prevent-generation-of-egg-archive
>> (lambda _
>> (substitute* "setup.py"
>> (("from setuptools impo
Ricardo Wurmus skribis:
> I stumbled upon a similar problem when building other Python packages.
> For ‘python-patsy’, for example, I found that an egg archive is produced
> no matter what I put in ‘setup.cfg’. As far as I can tell, “zip_ok”
> defaults to “0” in recent versions of setuptools, so
I stumbled upon a similar problem when building other Python packages.
For ‘python-patsy’, for example, I found that an egg archive is produced
no matter what I put in ‘setup.cfg’. As far as I can tell, “zip_ok”
defaults to “0” in recent versions of setuptools, so I don’t think the
fix you used on
Commit e5358a6 disables egg compression by augmenting ‘setup.cfg’ for
python-pillow only.
After:
--8<---cut here---start->8---
$ guix gc --references
/gnu/store/jx7dmdrsgndzic0jqqs9hsljgxgs95kw-python-pillow-2.8.1
/gnu/store/1hcg2k1lfz7z64p27cjm156jj8y6ia1s-py
The other day on IRC Ricardo and 宋文武 noted that python-pillow
currently comes with a compressed egg. Because it is compressed, the
daemon’s conservative scanning fails to see what store items it refers
to; in particular Ricardo noted that on his machine, python-pillow
refers to a non-existent stor
