On 2010/06/11 12:07, Will Maier wrote:
> Hi All-
>
> On Fri, Jun 11, 2010 at 06:02:03PM +0100, Federico G. Schwindt wrote:
> > On Fri, Jun 11, 2010 at 05:31:18PM +0100, Stuart Henderson wrote:
> > > On 2010/06/11 17:18, Edd Barrett wrote:
> > > > Index: pkg/PLIST
> > > > ===================================================================
> > > > RCS file: /cvs/ports/x11/tint/pkg/PLIST,v
> > > > retrieving revision 1.2
> > > > diff -u -p -u -r1.2 PLIST
> > > > --- pkg/PLIST 19 Apr 2010 13:55:56 -0000 1.2
> > > > +++ pkg/PLIST 11 Jun 2010 16:19:01 -0000
> > > > @@ -1,5 +1,7 @@
> > > > @comment $OpenBSD: PLIST,v 1.2 2010/04/19 13:55:56 edd Exp $
> > > > @bin bin/tint2
> > > > +...@bin bin/tint2conf
> > > > +bin/tintwizard.py
> > > > @man man/man1/tint2.1
> > > > share/doc/tint2/
> > > > @sample ${SYSCONFDIR}/xdg/
> > >
> > > Python scripts should be precompiled to .pyc bytecode and that
> > > should be also installed. You can use something like this:
> > >
> > > ${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py ${WRKSRC}
> >
> > for something outside site-packages?
>
> Yeah, I don't think that's useful here. If tintwizard.py is an executable
> script, it needn't be byte-compiled first (as that won't gain anything). If
> it's
> a module loaded by other scripts, then it should be byte-compiled (but
> installed
> in MODPY_SITEPKG, preferably).
Hmm. Untested but I suspect if someone runs it as root, it will leave
a .pyc around that pkg_delete won't remove..
