From: Michael B. <mic...@gm...> - 2005-10-06 19:40:54
|
On 10/7/05, Juanma <ju...@os...> wrote: > Hi Michael > > The ossim rpms we do publish in the web have been created using the > command rpmbuild, and using the spec provided in the web. Please tell me > about the python modules installed in a different place than expected in > the .spec file. #%{_libdir}/python2.3/site-packages/pyossim/ %{_datadir}/ossim-agent/pyossim/ #%{_libdir}/python2.3/site-packages/ossimframework/ %{_datadir}/ossim-framework/ossimframework/ > About the 3rd party rpms, they have been created using the src.rpm of > the packages and applying patches you can find in the contrib folder in > our source. No other file is required. Anyway we do not have any > disadvantage in publish in the web all the src.rpm, so everybody can > easily compile their own rpm files. For an example: the BASE spec file you refer to does pick up the source from what-ever you currently have installed. arpwatch refers to an tarball that is no longer available from their website etc... It's things like that I would like to avoid when I am building the next version of SIM CD... Also, could you please post your CVS commit messages in english so I, and the rest of the world, more easily follow the development process? As I don't know Spanish I can't follow the CVS development very well - which means that there is at least one less contributor to the code. Best regards Michael Boman -- IT Security Researcher & Developer http://proxy.11a.nu | http://www.boseco.com |