[Infrastructures] make install only?

[Bennett Todd]

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

2005-10-09T18:57:55 Daniel Hagerty:
>  > and actually running it from a third. What's more, work standards
>  > strictly prohibit an installed package making any reference to the
>  > build or install-staging areas.
>=20
>     At some level of remove, this is what any RPM package (or other
> packaging system) is going to do with python modules.

Precisely. In fact, at work we don't use software packaging as such;
it's a breathtakingly complex mix of a networked filesystem and
automated tools for pushing copies of stuff from one place to
another. But it's got that same essential install pattern as any
modern software packaging tool.

> Consider taking apart a few source packages to see how they deal
> with this problem in a systematic way.

Not being a Python user or fan, I don't know quite where to look.

I tried hunting a little, but all the packages I found delivered the
py and pyc files into /usr/lib/python2.x, and then package-wrapped
them from there, which is several steps of unusable for me; like a
well-wrapped rpm, I need to make install to a tmp dir, as a non-priv
user, and the final dir from which the code/libs are run needs to be
a completely arbitrary-seeming path ---
/foo/bar/something/baz/name/version/.

Anybody know of any well-written rpms for anything Python, that
don't just borf the libs into /usr/lib/python*?

-Bennett

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDSWxUHZWg9mCTffwRAlsWAJ9r9fq5eiFPBXbNzI20oG1JtjDqoACgrlwI
rJVud3+sUwoQgUNwLsnjFmE=
=kdXj
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--