I understand the wish to handle blivet's dependencies in blivet...hence the various
subpackage proposals.
The problem is that while they allow blivet to keep track of versioning they give less
benefit to clients of blivet. These clients are stuck in an all or nothing situation,
either they require blivet and all libblockdev plugins and dosfstools or they require
blivet alone and have to do all the management of other requires themselves.
Why not have blivet individually Suggest plugins and other optional dependencies, along w/
versions, since ultimately plugins may diverge? Make a single package or meta-package
which requires everything that blivet only suggests _and_ that anaconda will want to
require, e.g., all libblockdev plugins but not gfs2-utils. Call it blivet-anaconda. Maybe
blivet-gui will want a different set of dependencies...call that blivet-blivet-gui. Maybe
blivet-gui will want a different set of dependencies depending on what environment it
thinks it will run in. Call its meta-packages blivet-blivet-gui-1, blivet-blivet-gui-2...
Encourage any other clients of blivet that want a different subset of the tools that we
suggest to submit meta-packages with the same general naming scheme. I don't see why
we should have any difficulty in building these meta-packages.
I don't think this is a radically different suggestion from the two subpackage
suggestions above. The most significant difference is that it emphasizes that anaconda is
just one of several clients of blivet, and, because it really needs to be versatile, one
that wants to turn a lot of blivet suggests into requires.
It might make sense to add a few more suggests than there were requires in the blivet spec
file originally, e.g., for gfs2-tools.
--
To view this pull request on github, visit
https://github.com/rhinstaller/anaconda/pull/83