Re: [gentoo-python] Re: distutils-r1, setuptools and egg_info mess

[Michał Górny]

Dnia 2013-08-16, o godz. 22:14:30
Mike Gilbert <floppym@g.o> napisał(a):

> On Fri, Aug 16, 2013 at 4:11 PM, Michał Górny <mgorny@g.o> wrote:
> > The other solution is to put more hackery in the eclass. That is, find
> > all .egg files in ${S} and copy them to the future 'egg-base' for each
> > implementation. Then, we could keep both the separation of egg-info per
> > implementation and respect the initial contents.
> >
> > However, I'm not really happy to play that kind of games. Probably
> > the most proper place to put that logic would be 'esetup.py' function
> > but that would be just awful. Then there's
> > distutils-r1_python_prepare_all() which people still forget to call.
> >
>
> I actually think this might not be too bad. I don't often see
> conditional sources; more common are conditional install_depends,
> which end up in egg-info/requires.txt.
>
> I think it is relatively safe to copy *.egg-info/SOURCES.txt to
> BUILD_DIR. Here's a prototype:
>
> _copy_egg_info_SOURCES() {
>     local egg_info x
>     while read -r -d '' x; do
>         if [[ -f ${x}/SOURCES.txt ]]; then
>             egg_info=${x##*/}
>             mkdir -p "${BUILD_DIR}/${egg_info}" || die
>             cp "${x}/SOURCES.txt" "${BUILD_DIR}/${egg_info}/" || die
>         fi
>     done < <(find . -type d -name '*.egg-info' -print0)
> }

We should probably check what out of egg-info setuptools parse. If it's
just SOURCES.txt, and remaining files are written from scratch, there
is no point in playing with single files.

-- 
Best regards,
Michał Górny