[Distutils] Distutils changes - end user requirements (Was: Deprecate MANIFEST.in)

[Antonio Cavallo]

Hi,
I've been working on something similar with various approaches since a
long while.

I've finally got someting running on
http://download.opensuse.org/repositories/home:/cavallo71:/python-opt

It compiles on across different distribution but at the moment the
suse rpmlint checks are
too stringent and the compile fails (actually it works fine but it
doesn't release the packages).

Basically what I needed was (still is) a rpm integrated package to
install on any linux distribution
with a precise set of requirements:

1. The administrator should see the distro installed python (transparency)
2. The new "interpreter" should set on request the environment (explicit)
3. The installation should leverage the rpm infrastructure
(consistency in a running system)

These requirements are mandatory in order to garantee a smooth operation
on across systems.
Moreover a user shoudl use the distuils tools to install additional packages
without any "magic" (so python setup.py bdist_rpm should generate a
working installable package).

Basically to "activate" the new python interpreter all a user have to do is
typing something like:
$> . /opt/cavallo-python-2.6.1/cavallo-python-env.sh

(yes the name has to be changed at some point;))

Let me know if this sounds a good idea,

Regards,
Antonio Cavallo





I'm packaging python for linux in a separate deirectory and I needed
to be completely "system" trasnparent,

On Thu, Apr 9, 2009 at 8:54 PM, Trent Mick <trentm at activestate.com> wrote:
> Paul Moore wrote:
>>
>> On that note, didn't ActiveState distribute their version of Python
>> with a package manager (PPM)? As far as I know, that was only ever
>> supported by ActiveState themselves, no-one else ever built PPM
>> packages for their extensions, and it's been quietly dropped in recent
>> versions (Google tells me that it vanished around Python 2.3).
>
> Yes, it was there a long time ago. It was dropped around ActivePython 2.3,
> as you say, because it wasn't well architected and, at the time, we didn't
> have the resources to maintain it.
>
> However, we've just recently hired a full time employee to (in part) start
> looking at a "PyPM" package manager again -- this time with an appropriate
> architecture. The hope is to have something to show in the fall (perhaps
> sooner).
>
> Trent
>
> --
> Trent Mick
> trentm at activestate.com
> _______________________________________________
> Distutils-SIG maillist  -  Distutils-SIG at python.org
> http://mail.python.org/mailman/listinfo/distutils-sig
>