[oi-dev] pkglint fails during publish
    Gary Mills 
    gary_mills at fastmail.fm
       
    Tue May 12 16:19:30 UTC 2020
    
    
  
On Sat, May 09, 2020 at 02:12:25PM -0700, Alan Coopersmith wrote:
> 
> Upstream IPS fixed this by adding the -e flag to pkglint, so that
> consumers like ON/illumos could just do:
> 
> PKGLINT=       /usr/bin/pkglint -e $(ONBLD_TOOLS)/lib/python
> 
> https://github.com/oracle/solaris-ips/commit/b1d64c287c4346d2c5be5fe4cee278914ea86042
> 
> As a temporary workaround without that IPS comment, they could do something
> like:
> 
> PKGLINT=        PYTHONPATH=$(PYTHONPATH):$(ONBLD_TOOLS)/lib/python \
>                         /usr/bin/64/python2.7 /usr/bin/pkglint
That's approximately the solution that OI is using now.
> (Substitute python path as appropriate for the version of Python used in your
>  IPS builds.)
A better solution would be to install the pkglint module into the
standard location where Python searches for modules.  That would
always work.
-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-
    
    
More information about the oi-dev
mailing list