On Wed, Dec 11, 2019 at 2:37 PM Neal Gompa <ngompa13(a)gmail.com> wrote:
On Wed, Dec 11, 2019 at 3:25 PM Troy Dawson <tdawson(a)redhat.com> wrote:
> As the final bugs of modularity in EPEL 8 get worked out, I'm working
> on the plan for the kde modules. Right now, I'm leaning towards a
> great big kde module with all the kde packages in it. There would be
> two streams. rawhide and stable.
> rawhide would follow the fedora master dist-git branch. It would get
> updated at least once a month, or faster. No quicker than ever two
> weeks, because that's how long it takes for things to go through
> bodhi. I'm leaning towards once a month.
> stable would follow the stable Fxx branch, and get updated every three
> months, or when security and/or major bugs happen.
> The modules would have *all* the qt5 packages in them, including those
> that are in RHEL8. Because of this, we will not be able to mark them
> as "default". People will have to enable them to use them.
> I am currently working my way through all the packages, making sure
> they build and making fixes in rawhide/master when they don't. I
> think there should only be about 15 to 20 packages that need tweaking.
> Thoughts and/or comments?
I'm increasingly wondering if it's a good idea to ship KDE as a
module. The number of issues being discovered (including inability to
discover and deal with security issues) makes me think we might want
to consider shipping it as a normal set of packages...
The biggest reason for building it as a module is the qt5 packages in RHEL8.
If RHEL8 didn't have any of those, then I would completely agree with you.
If it's possible to have just those packages as a module, and the rest
without ... that might work too. But then you would have a weird
situation where you have lots of packages that look like they will
install, but won't because they require a different qt5 that what
But I'm not even sure if that will work. koji is going to see the
non-module packages, (from RHEL8) and use them for building.