On Wed, 2017-10-18 at 15:53 -0400, Eric D Helms wrote: > > 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?
There's two forms. For gems only used by the plugin, we add them to the package as a list of deps - see [1] for an example. Where more than one gem needs a dep, we move it to a separate package that can be depended on, e.g. deface [2,3] Greg [1] https://github.com/theforeman/foreman-packaging/blob/deb/develop/pl ugins/ruby-foreman-graphite/debian/gem.list [2] https://github.com/theforeman/foreman-packaging/tree/deb/develop/pl ugins/ruby-foreman-deface [3] https://github.com/theforeman/foreman-packaging/blob/deb/develop/pl ugins/ruby-foreman-column-view/debian/control#L11 -- 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.
