Re: [ANN] Spike Asset Manager release 0.13

2005-01-31 Thread David Fraser
mh wrote: Fredrik- This is a known issue. The tool currently only looks in certain locations or hints rather then spidering the whole hard drive (which could take a bit of time). If you have installed in a non-standard location (or are using a platform or version of software that hasn't been test

Re: [ANN] Spike Asset Manager release 0.13

2005-01-31 Thread mh
Fredrik- This is a known issue. The tool currently only looks in certain locations or hints rather then spidering the whole hard drive (which could take a bit of time). If you have installed in a non-standard location (or are using a platform or version of software that hasn't been tested agains

Re: [ANN] Spike Asset Manager release 0.13

2005-01-31 Thread mh
The idea is to have a framework to do this in a semi-crossplatform manner. The framework could be updated to know about apt, portage repositories as well as talk to to the windows registry. Not everyone is running redhat ;) -- http://mail.python.org/mailman/listinfo/python-list

Re: [ANN] Spike Asset Manager release 0.13

2005-01-31 Thread Fredrik Lundh
Skip Montanaro wrote: >Matt> Spike Asset Manager (SAM) is an open-source cross-platform >Matt> framework written in python for probing a system for components >Matt> and reporting them. > > That's a pretty generic description. Pardon my ignorance, but what's the > advantage over, for

Re: [ANN] Spike Asset Manager release 0.13

2005-01-31 Thread Skip Montanaro
Matt> Spike Asset Manager (SAM) is an open-source cross-platform Matt> framework written in python for probing a system for components Matt> and reporting them. Matt, That's a pretty generic description. Pardon my ignorance, but what's the advantage over, for example, "rpm -aq | gre

[ANN] Spike Asset Manager release 0.13

2005-01-31 Thread mh
Spike Asset Manager (SAM) is an open-source cross-platform framework written in python for probing a system for components and reporting them. It includes a driver file that probes for components commonly found in a LAMPJ stack (Apache, MySQL, PHP, Tomcat, etc). Note that the L in LAMP could be Li