Re: Rewriting pkglint in a portable language

["D'Arcy J.M. Cain" <darcy%NetBSD.org@localhost>]

On Thu, 24 Mar 2016 09:48:38 -0400
Greg Troxel <gdt%ir.bbn.com@localhost> wrote:
> That's fair enough - but it leads to a requirement to have multiple
> versions installed in parallel and manage that.  It's been troublesome

Which is easy with pkgsrc.  Multiple versions co-exist just fine.  Even
3.4 and 3.5 can co-exist.

> because may others thing "#!/usr/bin/env python" is ok, and soundness

Because I need two versions (and because I sometimes install code
written as if Linux was the only OS in the world) I put symlinks
into /usr/bin for python, python2 and python3.  The first can be a
symlink to whichever Python you want for your default.  I then use
"#!/usr/bin/python" in my scripts unless I need to guarantee a specific
version.  Pkgsrc is good about changing the "#!" to the actual
executable that the package requires.  For example, mailman uses
"#! /usr/pkg/bin/python2.7" for its scripts because they aren't ported
to 3 yet.  Pretty painless overall.

-- 
D'Arcy J.M. Cain <darcy%NetBSD.org@localhost>
http://www.NetBSD.org/ IM:darcy%Vex.Net@localhost