www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam R. B. Jack" <aj...@trysybase.com>
Subject Fw: ActivePython 2.3 and PyPPM
Date Fri, 31 Oct 2003 19:26:39 GMT
I think it is key we separate repository from "package indexing" (what is
'registered' on a machine) and "installation". I think these are awesome
goals, but weighty distractions we can't step up to. We'd need greater
community involvement than 'repository' ought have scope for. I'd like to
see these kept out of scope (for phase one at least). Thoughts?

BTW: I could see a complete solution/tool like Maven could use repository
along with it's own indexing/installation capability very nicely for it's
growing Java community. I could see how that is something achievable, and
valuable [ok -- cool.]. I just don't think it can be done generically (and
language independently) for repository.

As an FYI, something from the Python community:


----- Original Message ----- 
From: "Trent Mick" <trentm@ActiveState.com>
To: <activepython@listserv.ActiveState.com>
Cc: "Javier JJ" <python.tutorial@jarava.org>
Sent: Friday, October 31, 2003 11:24 AM
Subject: ActivePython 2.3 and PyPPM

> As you noticed, PyPPM is no longer part of ActivePython 2.3.x.  The
> fundamental reason for that change is that the old PyPPM infrastructure
> was not maintainable or scalable (keeping modules up to date was very
> painful and adding new modules even more so).
> Rather than keep patching a system which didn't fit in well with the
> core infrastructure for building and distributing Python packages, we
> think that everyone is better served if we spend a bit of time to figure
> out how to leverage some of the new developments in Python (such as
> PyPI, the Python Package Index and the wider adoption of distutils, the
> distribution package) to come up with a good next-generation system.
> Given our limited resources, we couldn't _both_ maintain the old system
> and work on the new one.
> In coming weeks, we'll try to reach out to the ActivePython community
> and figure out what _you_ think we should do when it comes to package
> management for Python (which input will naturally be combined with our
> opinions, resource constraints, etc.).  In the meantime, please send
> your thoughts to:
>     ActivePython-feedback@ActiveState.com
> Thanks for your input,
> Trent and the ActivePython team
> -- 
> Trent Mick
> TrentM@ActiveState.com
> _______________________________________________
> ActivePython mailing list
> ActivePython@listserv.ActiveState.com
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
> Other options:

View raw message