Chiming in kind of late here...
On Mon, Apr 1, 2019 at 9:08 AM qrsBRWN <qrsbrwn(a)uidzero.se> wrote:
On April 1, 2019 1:19:58 PM GMT+02:00, "Jan Staněk" <jstanek(a)redhat.com>
>On 31. 03. 19 14:11, qrsBRWN wrote:
>> This we need to get quickly to option 1 afterwards it may have served
>it's purpose though
>From my experience, creating module is rather time consuming, and I
>not yet wrapped my head around it properly. Although it is the correct
>way forward to have it shipped in Fedora, for quick'n'dirty packages
>testing purposes COPR may be better.
I believe using a COPR is best because this is a one time transition
period. Once f31 is released, sway will be updated just like everything
else. If the sway packages had made f30 I would have said to not even
bother with a COPR, but I forget that not everyone upgrades immediately.
Yeah modules is uncharted territory for me too. I'm thinking
lines that to get to a module we at least need a COPR for testing.
I will have to be pretty much a permanent fixture so there's no question
about where to get the correct version of the handful of packages that
needs to be tested together.
I found skimming over the modules docs interesting as somebody also new to
>If you are willing to create/maintain one, we could probably declare it
>the "official Sway SIG COPR", with a disclaimer "for testing purposes
>only" and a link to the module/installation instructions once they are