On 13/02/2019 09:48, Neal Gompa wrote:
On Wed, Feb 13, 2019 at 4:34 AM Tom Hughes tom@compton.nu wrote:
On 13/02/2019 09:11, Neal Gompa wrote:
On Wed, Feb 13, 2019 at 4:09 AM Tom Hughes tom@compton.nu wrote:
I don't think that second consequence is entirely true.
As I understand the the default module stream remains available in the main repo and hence would be installable with things that don't understand modules. There would be no ability to switch to an alternate stream with other tools though.
That's not true. If the modulemd isn't processed, all the RPMs are evaluated and the repo looks like a completely conflicting pile of nonsense. This is what makes PackageKit and dnfdragora scream. Though they don't crash on it anymore, which is a good thing. :)
Not sure I follow... I don't see anything called modulemd in the repodata and, for example, pkcon seems to be happy to install ant on my rawhide vm.
As I understand it modulemd is something which goes in a distgit repo to control how modules are built?
The fedora-modular repo has a modules.yaml.gz appended to it that is used for shipping module information for package managers to process for filtering rules.
Ahh I have the modular repo disabled, so that's all fine then ;-)
Tom