Re: Use of GNU userland during pkg builds [Was lang/npm PLIST errors]

To: Filip Hajny <filip%joyent.com@localhost>
Subject: Re: Use of GNU userland during pkg builds [Was lang/npm PLIST errors]
From: Adam <adam%netbsd.org@localhost>
Date: Fri, 11 May 2018 11:39:08 +0200

>>> => Checking file-check results for npm-6.0.0nb1
>>> ERROR: ************************************************************
>>> ERROR: The following files are in the PLIST but not in /usr/pkgsrc/lang/npm/work/.destdir/usr/pkg:
>>> ERROR: /usr/pkgsrc/lang/npm/work/.destdir/usr/pkg/lib/node_modules/npm/html/doc/misc/npm-coding-style.html
>> 
>> Not sure whether related, but also noticed the following error during
>> build:
>> 
>> find: -not: unknown option
>> 
>> GNU find has got above option, NetBSD base find doesn't have.
>> 
>> In general, is it advisable to set PATH of gnu userland ahead of pkg and
>> base, since most upstream build procedures assume Linux environment?
> 
> Thanks, I’ll check both problems today. I assume it’s just assumptions that upstream makes.
> 
> -F

My fault. I didn't know about '-not' not being supported. Fixed it and updated npm to 6.0.1.

Kind regards,
Adam

Follow-Ups:
- Re: Use of GNU userland during pkg builds [Was lang/npm PLIST errors]
  - From: Mayuresh

References:
- lang/npm PLIST errors
  - From: Mayuresh
- Use of GNU userland during pkg builds [Was lang/npm PLIST errors]
  - From: Mayuresh
- Re: Use of GNU userland during pkg builds [Was lang/npm PLIST errors]
  - From: Filip Hajny

Prev by Date: Re: x11 clashes of base and pkg [Was Re: Confusing versioning scheme of freetyp2?]
Next by Date: Re: Use of GNU userland during pkg builds [Was lang/npm PLIST errors]
Previous by Thread: Re: Use of GNU userland during pkg builds [Was lang/npm PLIST errors]
Next by Thread: Re: Use of GNU userland during pkg builds [Was lang/npm PLIST errors]
Indexes:

Home | Main Index | Thread Index | Old Index