Next steps towards a module

[qrsBRWN]

The packages from the sway-sig copr seems to behave as expected thus far.
What are the next steps on the route to modularity?
Are there test cases from the regular sway packaging we can reuse?
Is there any special hoops to jump through?

Br
Markus

[Jan Staněk]

On 20. 04. 19 17:57, qrsBRWN wrote:
> What are the next steps on the route to modularity?

Probably creating and testing a modulemd file; see [1] for docs.
> Are there test cases from the regular sway packaging we can reuse?

The packages are built as normal, only in "different context" (AFAIK).
So any tests included in the packages will be run.
Not sure if this answers your question, though :)
> Is there any special hoops to jump through?

Well, the last time I tried, the module building in COPR did not work,
and neither did the local module build. I have forgotten the details,
but if you run into similar issues, try asking on the relevant channels
(COPR/Modularity MLs) – you are not alone :)

Good luck!

[1]: https://docs.fedoraproject.org/en-US/modularity/

[Till Hofmann]

Hi all,

sorry for not being more active, I'm quite busy with other things at the
moment.

I'm totally in favor of the idea of creating a module. If nobody has
done so, I'd start working on that next week.

Kind regards
Till

On 4/20/19 5:57 PM, qrsBRWN wrote:
> The packages from the sway-sig copr seems to behave as expected thus far.
> What are the next steps on the route to modularity?
> Are there test cases from the regular sway packaging we can reuse?
> Is there any special hoops to jump through?
>
> Br
> Markus
>
> Sway mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]