On Sat, 2017-10-14 at 14:24 -0400, Eric D Helms wrote:
> Note: This is specific to RPMs because as far as I know the Debian
> process is different and uses gems directly. Please correct me and
> contribute any information with respect to Debian that I miss. I
> believe the Nodejs part of the email does apply to Debian.

As Michael says, I think we can mostly leave Debs out, at least for
now.

> 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.

If we go for option 2 below, then vendoring an npm install at build
time (as Michael said, we do this for Debian) feels like a better
option.

If we go for building our own SCL, then +1 for this.

> Ruby Gems
> 
> Option 2, to vendorize, is a deviation from our prior practices in
> the area of production deployment. Thus, I am reaching out to the
> community to get feedback. One interesting consideration for
> vendorizing is when containers are considered and having the ability
> to build them using 'bundle install' versus using RPM based
> installation.

Vendoring hasn't (to my knowledge) caused many issues for Debian users
(Michael?), and having consistent build processes makes it easier for
anyone to support users on different OSs.

That said, I've not really been involved with the RPMs, so I'm unsure
if this causes a bigger headache for Yum users than Apt users. I'm also
unsure of the work required to create an SCL, but if it's non-trivial
then I'd be looking to CentOS to collaborate on a Rails SCL for
everyone to use - for just ourselves, then vendoring seems easier.

Greg

-- 
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.

Reply via email to