Gustavo Sverzut Barbieri wrote: > --- Dirk Meyer <[EMAIL PROTECTED]> escreveu: >> Gustavo Sverzut Barbieri wrote: >> > I vote for something different: >> > >> > src/* -> <prefix>/lib/python<version>/site-packages/freevo >> >> Yes, I thought about that. That's the reason why I want to clean this >> up. As you said, it should still be possible to run freevo from a >> directory conatining everything. To make both possible, I want to >> move >> all python files to src so that it is easier to find (src or the >> python site-package path). > > It's kind difficult to tell what is right and what is wrong there. If > we have everything in site-packages, it will be automatically usable, > just do "import". So I vote for that...
OK > > >> > skins/main1 -> <prefix>/share/freevo/skins/main1 >> >> That's no share, that's code! > > I know, so should it be in site-package? we could add: > <prefix>lib/python<version>/site-package/freevo/skins/main1 Yes. And to make it easier when you don't install it, I wanted to move skins/main1 to src/skins/main1. src should be identical with site-package/freevo > > >> > skins/icons -> <prefix>/share/icons/freevo >> > skins/images -> <prefix>/share/pixmaps/freevo (or in icons) >> > skins/xml/type1 -> <prefix>/share/freevo/skins/main1/xml (since >> those >> > xml should be specific to that skin code) >> > skin/fonts -> <prefix>/share/fonts/freevo (or just share/fonts) >> >> Better install everything from our share (if we rename skins to >> share) >> to $prefix/share/freevo. > > I don't like to make our skins -> share/freevo. We should keep it like > a subdir: share/freevo/skins/ You lost me. What to put there? >> Again, it's easier if we install everything >> from one directory of our tree into one directory in prefix. It's >> much >> easier to find things when we support directory-based and installed >> versions of freevo. > > IMHO we should change our CVS to like that, so our cvs will be <prefix> > and there we should have share/skins, lib/python/site-packages/ (this > look ugly, maybe for this we could strip site-packages?), ... > > >> > helpers/ -> <prefix>/share/freevo/helpers >> >> Like main1, it's code. > > Who said share should not have code in it? I think the LSB does. You could put the helpers into lib I guess. > From what I know, helpers aren't used directly from freevo (if they > are, so put them in freevo site-package). Take a look at share/dia, > share/gnumeric, share/pgsql, share/php, all of them have scripts > that are related, but not direct used by them. But many use the freevo environment (e.g. import config). I just fixed the freevo start script to call the helpers with the correct PYTHONPATH. You shouldn't call imdb.py in helpers, you should call 'freevo imdb ...'. > Sure... IMHO we shoul have something like: > <lib>/skins/main -> <share>/skins/main/ (all the xml/fxd goes here) OK, so we put main there and all main fxd files (== all) into share/skins/main. > Others (example): > <lib>/skins/barbieri -> <share>/skins/barbieri/ You lost me again. barbieri is now the engine (python code), right? > Also, we should put freevo (main app) in <bin>, so you don't have to cd > $FREEVO_PATH; ./freevo Take a look at the new freevo script. It supports knowledge about where all the python stuff is (right now src). We could search in <scriptdir>/../share/freevo. <scriptdir> will be $prefix/bin Dischi -- Drugs cause amnesia and other things I can't remember... ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
