[Distutils] Setuptools' goal in rpm/deb-based systems

[Jeff Pitman]

On 12/29/05, Kevin Dangoor <dangoor at gmail.com> wrote:
> On 12/29/05, Jeff Pitman <jeff.pitman at gmail.com> wrote:
> > On 12/29/05, Kevin Dangoor <dangoor at gmail.com> wrote:
> > > TurboGears
> > > 0.9 makes use of setuptools' extension mechanism which is why the egg
> > > metadata needs to be available.
> >
> > During runtime or during installation?
>
> During runtime. Certain parts of TurboGears can be extended just by
> installing an egg with the additional functionality. TurboGears itself
> uses this mechanism to define the base pieces. (tg-admin commands are
> an example of this: anyone can create an egg that adds tg-admin
> commands. the existing commands are all defined in the same way that a
> user would create commands.)

So, they're plugins that extend tg-admin commands. In the .rpm/.deb
space what would happen here is that these plugins would also be
installed as .rpm/.deb. This is kind of like Twisted 2.0+ after the
split. What would be good here is to have .eggs install into $HOME and
tg-admin still pickup on them.

--
-jeff