On Tue, 2019-09-03 at 14:03 -0700, Arjan van de Ven wrote:
On 9/3/2019 1:38 PM, VanCutsem, Geoffroy wrote:
> On Tue, 2019-09-03 at 09:44 -0700, Simental Magana, Marcos wrote:
> > On Tue, 2019-09-03 at 09:40 -0700, Auke Kok wrote:
> > > On 9/3/19 9:18 AM, VanCutsem, Geoffroy wrote:
> > > > We are using, amongst other tools, Graphviz to generate the
> > > > ACRN
> > > > documentation. However, there are some plugins missing if you
> > > > install
> > > > the 'graphviz' bundle. Looking at the graphviz packaging
file
> > > > [1], they
> > > > are in an rpm called 'graphviz-extras'. But the only way I
> > > > could
> > > > find
> > > > to install these was to add the 'desktop-apps' bundle
(which
> > > > is
> > > > rather
> > > > large).
> > > >
> > > > I'm not sure I fully understand the 'also-add' mechanism
but
> > > > would it
> > > > appropriate to add something like 'also-add(graphviz-extras)'
> > > > to
> > > > the
> > > > graphviz bundle definition [2]?
> > >
> > > I'm fairly sure also-add() only works right now for bundles,
> > > not
> > > subpackages, so we can't just yet do that.
> >
> > We could go with a graphviz-extras bundle instead, which makes a
> > lot
> > of sense in
> > this case.
> >
> > Thoughts?
> >
>
> That works for me. Another option would be to just include these
> "extras" libraries into the graphviz bundle directly and have one
> bundle that has it all.
they pull in the kitchen sink due to their dependencies
Fair enough, would a new 'graphviz-extras' bundle be the best way
forward?