On Mon, Jun 26, 2017 at 4:06 PM, Petr Šabata <contyk@redhat.com> wrote:
>
> The modular release is effectively a separate distro.
>
> While using single RPMs from traditional Fedora might work in
> most cases, I wouldn't recommend enabling the entire repository
> which also provides packages conflicting with (and possibly
> updating) those provided by modules.
>
> Creating logical modules would be the best approach here.
> Containers are also an option but someone needs to make them, too.
>
> P
Perhaps I'm confused or have outdated information, but I thought I
recalled reading plans to (at least initially) potentially throw all
non-already-module'd packages into something like an "Everything"
module so it continued to be installable? And then gradually migrate
things out from it into modules.
It seems like doing so would solve this problem.
Many of the packages I maintain are essentially one-offs that I'm not
convinced will ever belong in a specific module-- where would things
like this end up?
Ben Rosser
We talked about this with the server wg and decided for F27 server we would try to avoid an "everything else" module and figure out how to solve this problem more nicely between now and release. We have multiple options here including : generating modules for everything, making an extra repo of stuff available, leaving non-modules out, and, finally, the everything else module.
Definitely a recognized issue, but not sure we are decided on the answer (or answers). We would like the module guidelines to address the use cases with recommendations but it is tough to iron this out.
Langdon