Manuel Bouyer <bouyer%antioche.eu.org@localhost> writes:
>> So I say back out 1.9 and then things are ok. wiz and oskar copied to
>> explain if I'm confused.
>
> Makefile is not the only thing to back out; PLIST needs to be backed out too:
>
> -${PYSITELIB}/pygrub-0.6-py${PYVERSSUFFIX}.egg-info
> -${PYSITELIB}/xen-3.0-py${PYVERSSUFFIX}.egg-info
> +${PYSITELIB}/pygrub-0.6-py${PYVERSSUFFIX}.egg-info/PKG-INFO
> +${PYSITELIB}/pygrub-0.6-py${PYVERSSUFFIX}.egg-info/SOURCES.txt
> +${PYSITELIB}/pygrub-0.6-py${PYVERSSUFFIX}.egg-info/dependency_links.txt
> +${PYSITELIB}/pygrub-0.6-py${PYVERSSUFFIX}.egg-info/top_level.txt
> +${PYSITELIB}/xen-3.0-py${PYVERSSUFFIX}.egg-info/PKG-INFO
> +${PYSITELIB}/xen-3.0-py${PYVERSSUFFIX}.egg-info/SOURCES.txt
> +${PYSITELIB}/xen-3.0-py${PYVERSSUFFIX}.egg-info/dependency_links.txt
> +${PYSITELIB}/xen-3.0-py${PYVERSSUFFIX}.egg-info/top_level.txt
That's changing the form of the egg files.
I think the other thing egg.mk does is to depend on setuptools. Perhaps
that should be added.
> Now I've no idea what the difference bwteen extention.mk and egg.mk
> is and why egg.mk would be better (will extention.mk be deprecated at
> some point ?). If going back to extention.mk is not considered a step
> backward, then it's probably the way to go.
I do not expect extension to be deprecated.
If somebody wants to split egg into egg-with-build-for-one-egg and
egg-without-build-possibly multiple, and then reconsider this sort of
change, I'd say tech-pkg@ is open for proposals.
We can see if there's an explanation why not to revert in 24h.
Sort of separately, and partly because the world is too complicated, I
would be inclined to add PYTHON_VERSIONS_INCOMPATIBLE=27 to xentools. I
don't see any reason to build it with 2.7, and 2.7 ends up with
different versions of some things, like an ancient version of
setuptools, and that's just complexity we don't need.
Attachment:
signature.asc
Description: PGP signature