On Thu, 18 Oct 2012 16:12:55 -0700
Brian Harring wrote:
> On Thu, Oct 18, 2012 at 11:54:21PM +0200, Micha?? G??rny wrote:
> > On Thu, 18 Oct 2012 02:15:43 -0700
> > Brian Harring wrote:
> >
> > > There's a trick to this; currently, those generated scripts hardcode
> > > the allowed/known pytho
On Thu, Oct 18, 2012 at 11:54:21PM +0200, Micha?? G??rny wrote:
> On Thu, 18 Oct 2012 02:15:43 -0700
> Brian Harring wrote:
>
> > There's a trick to this; currently, those generated scripts hardcode
> > the allowed/known python versions for that package. We obviously have
> > to preserve that;
Ah, and a minor note.
On Thu, 18 Oct 2012 02:15:43 -0700
Brian Harring wrote:
> /usr/libexec/python/wrapper upon invocation, takes a look at argv[0];
> sees how it was invoked basically. This will be the /usr/bin/whatever
> pathway. It reads the symlink, in the process getting the allowed
>
On Thu, 18 Oct 2012 02:15:43 -0700
Brian Harring wrote:
> There's a trick to this; currently, those generated scripts hardcode
> the allowed/known python versions for that package. We obviously have
> to preserve that; I propose we shove it into the symlink path.
>
> Basically, we add a /usr/
On Thu, Oct 18, 2012 at 08:02:42AM -0700, Brian Dolbec wrote:
> On Thu, 2012-10-18 at 02:15 -0700, Brian Harring wrote:
> > On a related note; we currently install multiple versions of the same
> > script- the only difference being the shebang. If one ignores the
> > shebang, in some cases this
On Thu, 2012-10-18 at 02:15 -0700, Brian Harring wrote:
> If folks haven't looked at python_generate_wrapper_scripts in
> python.eclass, I'd suggest doing so. For examples of it's usage, grep
> for 'python_generate_wrapper_scripts' in /usr/bin/; any place you see
> it, look for -${PYTHON_TARGET
