> Mikolaj Izdebski wrote:
> This is exactly what I feared when the modules were first proposed:
> essential packages moving to modules only.
> I think this is absolutely a step in the wrong direction. Things like "ant"
> are essential parts of a distribution. They cannot sit in some module with
> arbitrary branches that can be EOLed at any time.
> Kevin Kofler
As far as I can understand the modules idea and while looking into those yaml files of ant
and cmake for instance, I fail see why modules should work without any spec file and
therefore also why without rpmbuild. The modules idea seems to be more about how to have a
possibility to build a bunch of packages in their own dependency tree for a custom branch
(and on which base system that branch should ever work). So in my opinion, modules can
never work without any base system built completely from without modules.
What I like about modules is that it obsoletes the need to check for the target
distribution inside of the spec file (that's now handled with a branch in git). What I
don't like is that all dependencies have to get repeated in the yaml file. What real
problem do we try to solve?
Please calm down and just my 5ct.