Wow Dischi; very impressive. I'm going to make a proper Debian package
now that it'll be easy.

On Fri, Aug 22, 2003 at 08:54:04PM +0200, Dirk Meyer wrote:
> I just fished (and tested) the python setup.py script. You can now
> install Freevo into your system, no need to install it into
> /opt/freevo or another strange location. You have three choices now: 

> o ./freevo setup dumps the freevo.conf not in the local directory
>   anymore. It ries to use /etc/freevo, if that fails it takes
>   ~/.freevo

Good news; I would think some people might want to run the binaries
from read-only media or partitions; if /var and /etc are writable,
they'd be fine; though I guess in practice, only /var should need to
be writable after the initial configuration.

> o setup.py doesn't install 'testfiles'. I don't see a reason for that 

Agreed; if you're testing, you can run it from a directory. Once
you've got it installed, you presumably don't need them. Are we going
to pull them out of CVS and just make a tar.gz for people then?

> o Right now every helper and everything in contrib is installed to the
>   share directory. This should be cleanup up: move python helpers to
>   src/helpers, delete helpers a user won't need (or noone needs) and
>   we should only install the needed files in contrib.

contrib typically goes in /share for most of the apps I've installed;
unless they're binaries, in which case, they should be in
lib/freevo...

> o Now something to discuss with Aubin (Hi Aubin): I want to remove the
>   -OO again. It only speeds up things on startup. If you want this,
>   you can set an environment variable. Why I want remove this? Python
>   tries to make pyo files of all files where such file is
>   missing. When running Freevo as root, Python dumps pyo files of all
>   system py files into site-packages. Gentoo can't remove them when
>   you want to remove the package because they weren't there when the
>   Installation took place. I guess we have the same problem with other
>   distros. 

Not under Debian, because they should be compiled on install, and
removed on uninstall... all Python packages under Debian can do this:

        dpkg -L python2.3-mmpython |
                        awk '$0~/\.py$/ {print $0"c\n" $0"o"}' |
                                        xargs rm -f >&2

If Gentoo keeps a packing list of installs, something similar should
work. It's not a big deal to me, because it's up to the end user, but
it's not just startup that should be sped up by this; anything would
be sped up, since it's being compiled into native binaries (unlike
pyc, which are portable)

I know of at least one RPM that behaves like this.

As I said, I'll be building my packages this way, and running it this
way, but if it's difficult or impossible to do on certain Distro's, I
don't want it to be an issue for people.

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