On Wed, Oct 18, 2017 at 3:01 PM, Michael Moll <[email protected]> wrote:
> hi, > > On Tue, Oct 17, 2017 at 03:42:50PM -0700, Dmitri Dolguikh wrote: > > > 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) > > > > Not sure if this has already been considered: use bundler to package the > > app. In this case all dependencies, including rails will be cached > locally, > > and we could then wrap the result into an rpm. Not sure how plugins would > > fit into this though. > > I'm not 100% sure if you meant it like that, but basically this is what > we're doing in the current DEB approach. The "foreman" package is the > result of "bundle package", the subpackages drop in a file or two each > into bundler.d/ and a plugin package is its gem (and if needed, > dependent gems) to add into the current bundle and precompiled assets. > How do the plugins isolate their dependent gems? i.e. is it a script or build tool or just knowledge to grab the right gems and pop them in? > > 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. > -- Eric D. Helms Red Hat Engineering -- 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.
