On 3/5/19 9:08 AM, Adam Samalik wrote:
On Mon, Mar 4, 2019 at 10:26 PM Michael Cronenworth <mike@xxxxxxxxxx> wrote:
On 3/4/19 3:04 AM, Petr Šabata wrote:
You can view them as virtual repositories with dependencies. I
think that might be the simplest way to put it.
You can try playing with fedmod to generate your modulemd file or
you can just write it from scratch; it's not all that complicated.
Why should I care? Please, win me over. (I'm being serious.)
I think you should care if:
a) You need to maintain multiple versions of the same app/runtime/set of
tools tools in Fedora (or an alternative to something that already exists),
or
b) You only want to maintain one source branch per package for all Fedora
releases, or
c) You could benefit from having a build recipe in case you maintain
app/runtime/set of tools tools represented by multiple packages that need
to be built in the right order
But if any of the above is something that you need/want to do, then
Modularity won't help you nor hurt you in any way.
All of what list above can be handled at the rpm-level by means of
"proper" system integration.
That said, to me, modules are an approach to circumvent system integration.
Ralf
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
