--==========C0A2A2DEB47F462E91E5==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

>> 1. You might want to re-add that:
>>    ${INSTALL_DATA_DIR} ${EPYDOCDIR}
>>    So, that ${EPYDOCDIR} with correct permissions, user and group.
>
> I took that out on someone else's suggestion.  Anyone want to be a
> tie-breaker  on this?  Python distutils is supposed to take care of this.

distutils takes care of the ${PYSITELIB} stuff. I'm talking about about the =

documentation you're installing/copying into ${EPYDOCDIR} in the=20
post-install target. ${PAX} creates ${EPYDOCDIR} while copying the files,=20
but I'm not that sure if they get the correct owner and mode then.=20
Therefore I suggested the seperate ${INSTALL_DATA_DIR} step.

> I'm agnostic on this subject but it seems that the feeling generally is
> not to  add the extra layer.

Hmm. ;-)

--=20
Marc Recht
--==========C0A2A2DEB47F462E91E5==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAZxxn7YQCetAaG3MRAsDCAJ0TdNauzAnhMT0mlfilB9JP/7UILQCggZFY
boKQKknh07YMWPPxqwSx7ow=
=Sqah
-----END PGP SIGNATURE-----

--==========C0A2A2DEB47F462E91E5==========--