So nodejs_modulesdir (is it really "/usr/lib/node_modules ?) is not defined (as it’s actually creating%{nodejs_modulesdir} as a directory name) , add to the project config is probably the easiest option, else in the spec file add;
sure we can define the
%define nodejs_modulesdir /usr/lib/node_modules
in the spec file…but…should that not be solved upstream? Why is it defined for 13.2, but not for 13.1, SLE or Leap?
sure we can define the
%define nodejs_modulesdir /usr/lib/node_modules
in the spec file…but…should that not be solved upstream? Why is it
defined for 13.2, but not for 13.1, SLE or Leap?
Hi
Missing build requires… for the nodejs_modulesdir macro.
-------------------------------------------------------------------
Thu Oct 9 15:06:49 UTC 2014 - jgleissner@suse.com
- removed macros.nodejs (moved to nodejs-packaging)
So add a conditional…
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.51-52.31-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
malcolmlewis;2743234 Wrote:
> Hi
> Missing build requires… for the nodejs_modulesdir macro.
> >
Code:
> >
> -------------------------------------------------------------------
> Thu Oct 9 15:06:49 UTC 2014 - jgleissner@suse.com
>
> - removed macros.nodejs (moved to nodejs-packaging)
>
> >
> So add a conditional…
>
So, that worked, and the SLE based packages build. Problem comes now on
installation:
Code:
Problem: npm(bower) >= 1.4.1 benötigt von
tryton-sao-3.8.1-11.1.noarch wird nirgends zur Verfügung gestellt
nodejs-npm is installed - is npm (bower) a different npm?
Hi
Yes npm is it’s own package (well in Leap) and nodejs-npm (Bundled), so
I guess some conflict between releases needs to be sorted?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
nodejs is…odd. bower is a ‘plugin’ for npm. npm is available.
The tweak was to add a
Provides: npm(bower)
to let the build run through.
But then there is a problem with the content of
%{nodejs_sitelib}/*
Its empty. No idea why. In the installation from source, grunt runs afterwards and installs a lot of stuff. How to incorporate this in the build process? Analyzing this and adding each package as requirement? Seems that the nodejs stuff is not really made for packaging…
Hi
On your project page for the package, click on say the Leap build on the right, then it will show you all the built rpms, then click on the offending rpm. This will show a summary page of all the provides/requires for the package. Any of the missing ones will need adding if the package doesn’t detect them in the build process.