On Fri, Feb 20, 2009 at 1:25 PM, <[email protected]> wrote: > > But does pyglet necessarily know where it is installed? > Yes, it does. >
Are we sure about that for all cases? I have the default pyglet installation in /Library/Python/2.5/site-packages, and development versions in several locations on the hard drive. Currently they all use the save version of AVBin, but this isn't always necessarily the case. > > And should we arbitrarily prevent the user from installing it in one of > the others? > That's not what I was suggesting. That would be a Bad Thing. > > Are you working on a patch to implement this, Tristram? Why all the > discussion? > I would argue the current behaviour (hardcoded path to AVBin) is an unfortunate hack, and should be remedied. As is, I can't use the standard OS mechanisms (LD_LIBRARY_PATH, DYLD_LIBRARY_PATH or DYLD_FALLBACK_LIBRARY_PATH) to replace the default AVBin. Replacing this with a hack to another non-standard location seems like a decidedly less than ideal solution. -- Tristam MacDonald http://swiftcoder.wordpress.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
