On Sat, Aug 23, 2003 at 10:39:02AM +0800, Wan Tat Chee wrote:
> Wow, that's a pretty major revamp of the installation process. Looks like
> a fresh RPM spec file is needed. I'll have to digest it slowly :) 

It should make life very easy, since it's a standard Python module, so
if you examine the spec for any python module, you'll be half way
there :)

> I'm not familiar with the boot scripts, who's maintaining them? I do know
> that they're not chkconfig compliant though (missing some lines in the
> header). There's also a lirc-related file in the ./boot folder. Not sure
> if it should still be around.

They're not chkconfig compliant, because they're distro-neutral, which
means they have to be lowest common denominator. When I added them, my
goal was to have people make them into distro-specific versions, and
it's happened in some cases.

> Since I'm using the runtime python, *.pyos in the runtime directory are
> generated automatically during the installation process anyway. I suppose
> it would affect setup which doesn't use the runtime though.
> 
> My problem was that freevo_python gives a GLIBC_PRIVATE symbol error when
> running the compiler/optimizer. It doesn't occur with normal freevo
> invocation.

The system-wide Python really should be used I think; Python 2.3 is
available for every distro from rpmfind, debian, gentoo, slack, etc.

Aubin


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to