On Wed, Oct 08, 2003 at 11:16:26AM +0800, Wan Tat Chee wrote: > That is done for the freevo-src RPM package (to be released). However, we > also wanted to provide a full binary package for those who want to avoid > downloading numerous RPM packages (take a look at the new SF download page > for the freevo-deps packages -- it's only a partial list!). > > Hence my question/comment on putting stuff in /usr/local/freevo as was > done in 1.3.4 for the full binary package.
In that case, you're probably better off putting everything in one place. The advantages of putting Python and the modules in system locations are reduced if you have to use a single place for libraries. I think of it as an all or nothing deal; either you want a system install or you don't, so to maintain consistency, I would suggest using /usr/local/freevo for the package+runtime, and if you have time, making a seperate system-wide LSB-compliant one. Aubin ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
