Re: [Fink-beginners] Mnemosyne port ?
"Daniel Macks" <[email protected]>
| Newsgroups | gmane.os.apple.fink.core |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 02 Feb 2012 08:11:35 -0500, Alexander Hansen <[email protected]> wrote: -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2/2/12 6:56 AM, Martin Costabel wrote: > > On 2/02/12 03:27, Alexander Hansen wrote: [] > >> It looks like mnemosyne really needs one to use the built-in > >> Python. We don't actually do modules for that because they're not > >> very compatible with Fink's approach of using a self-contained > >> directory structure. > > > I propose to use the directory > /sw/Library/Python/x.y/site-packages/ > > > I have been doing this (surreptitiously and, according to the > fink > validator, illegally) for the pil-systempythonxy package for > quite > > a long time. It works well, if one places Runtimevars: PYTHONPATH: > > %p/Library/Python/x.y/site-packages into the package description. > > Let's take this to -core (especially as it's a fait accompli at this > point :-) ). > > Should we add %p/Library to the list of legal directories within the > Fink file hierarchy, for packages that build against the system's > toolkits? (I could envision %p/Library/Python, %p/Library/Tcl, ...) > > I see no problems with setting PYTHONPATH within a wrapper script for > an executable, so such packages use that location for their scripts > shouldn't be a problem. > > I'm a bit concerned about having to set PYTHONPATH globally, however, > though it seems like there aren't any good alternatives. This doesn't > produce any interference with Fink's python packages? Doesn't setting PYTHONPATH globally mean that *all* python interps will see it (including fink's pythonx.y and also python!x.y) and also see it with higher precedence than any fink-python-specific one as well? Doing it as a Runtimevars also means you presume no other package would also want to place python modules at some nondefault location (because it *sets* the variable rather than prepending to it). That seems like the logical approach that a "simple python program that has some private-use modules" package maintainer would take who doesn't feel like writing a wrapper or writing a -pyXX module. For example installing pil-systempythonXX breaks gildas (a good example, along with root5, of the safe way to alter a public-use env var). dan -- Daniel Macks [email protected] ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ fink-core mailing list [email protected] List archive: http://news.gmane.org/gmane.os.apple.fink.core Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-core