On Mon, Oct 26, 2009 at 09:18:25AM -0500, Olemis Lang wrote:
> 
> On Mon, Oct 26, 2009 at 9:03 AM, Roger Oberholtzer
> <roger.oberholt...@gmail.com> wrote:
> >
> > My Trac packages are installed in /usr/lib/python2.5/site-packages
> >
> > When I do an update of a package (python setup.py install), I see that I
> > get a new .egg (file or directory), but the old one is also still
> > present. In Trac admin, I only see the most recent one.
> >
> > My question is:
> >
> > 1) Should I be using something other than "python setup.py install" when
> > doing an update?
> >
> > 2) What is the best/correct way to remove the obsolete eggs?
> >
> 
> That goes beyond the scope of Trac itself and is related to setuptools .
> 
>   - The simple answer is «today there's no way to remove packages
>     installed using setuptools or easy_install».

No easy way, at least.  You can always edit easy_install.pth and remove the 
eggs with rm

>   - The continuation is «Python devs are working on that and many
>     other things in the upcoming Distribute module».
>   - My suggestion is «if package is available in your OS pkg manager
>     (e.g. apt on Debian, rpm on RH, ...) then use it »
>   - Open issues «when Trac will take benefit of all these improvements ?»
>     «what changes are needed ?» ... I just don't know :-/
> 
> -- 
> Regards,
> 
> Olemis.
> 
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
> 
> Featured article:
> Looking for a technique to create flexible, graphical dashboards ...
> - http://feedproxy.google.com/~r/TracGViz-full/~3/QO5N8AG0NnM/d6e3b3fd323d5b52
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to