Hi, On Sat, Oct 14, 2017 at 02:24:58PM -0400, Eric D Helms wrote: > Node/NPM Packages > > [...] > > Proposal: > Deprecate nodejs packages in favor of foreman-assets or a new RPM > foreman-node-modules that contains a source tarball of node_modules/ > packaged into a simple RPM that is used as a build dependency. This tarball > would be regenerated, and the package bumped, as dependency updates are > needed.
I do see a problem to apply this to Debian. There are "native extensions" (or whatever is the correct term in the Node world), used i.e. by node-sass that differ by architecture and Node API versionn. Gor Debian we're building on various architectures and also it's not 100% sure the same Node version is used (esp. it's often a different version than the one coming from EPEL). However, I don't see a problem with just leaving the Debian build process as (which is just a npm install at package build time). > Today we package all required rubygems as RPMs and utilize a thirdparty > Software Collection (SCL) for both the Ruby (rh-ruby22) and Rails stack > (sclo-ror42). The team that manages the RHSCLs has already released Ruby > 2.3 and RUby 2.4 SCLs and will continue to do so. However, there are no > plans to release any further SCLs for the Rails stack. This means, in > addition to our own dependencies, we need to build and manage the Rails > stack for the versions we want. This adds more packaging burden on the RPM > side. GIven this, we have a few options: > > 1) Build and manage our own SCLs for every version of Rails from here on > out > 2) Vendorize Rails and thirdparty gems into a one or more base RPMs > (e.g. an RPM for rails stack and one for thirdparty dependencies) I don't really have stakes in RPMs, but I'd try to stick with option 1 and I even expect that there's some demand for Rails SCLs at least in the RHEL/CentOS world by other projects, too. Regards -- Michael Moll -- 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.
