On 07/21, Daniel Lobato Garcia wrote: > 3. Put node_modules in a new package (foreman-npm-assets?) that > foreman-assets %install section puts in the right place? > > - Upsides: > - relatively easy to do > - jenkins can automate it > > - Downsides: > - less control or information for users about what's installed with > foreman, although we could specify the dependencies under > "Provides: bundled-npm(xxxx)" > > - Success with POC: haven't tried
Update - I tried to make a POC for this quickly https://github.com/theforeman/foreman-packaging/pull/1240 I think it could work if there's a way of telling RPM to not care about the requirements -i.e: it notices there are multiple npm(tap-stream) versions and complains about that... To be fair I didn't expect RPM to read the contents of %{nodejs_sitelib} and figure out all the dependencies! -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
