Re: i3wm for EPEL8
On Tue, May 19, 2020 at 10:47:57AM -0400, Eric Mesa wrote: > So...what is the proper path to get the perl folks to create epel8 branches > in their repos The same as with any other package: File a bug into Bugzilla. -- Petr signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: i3wm for EPEL8
Hi Eric, first and foremost sorry about not replying to the Bugzilla bug earlier, the past weeks were unfortunately a bit crazy. Eric Mesa writes: > Hey there, > > I noticed that the i3 window manager wasn't available in EPEL8. Before > trying to go through the process of becoming a package maintainer I decided > to try and run it via copr to see how much modification was needed. For > EPEL8 (as opposed to 7) I was able to take the current spec file and, after > creating an EPEL8 copr repo for xcb-util-xrm ( > https://copr.fedorainfracloud.org/coprs/djotaku/xcb-util-xrm/), it would > build. But it wouldn't install for it needed some perl packages. So I set > about building those. You can see how far I got in ( > https://copr.fedorainfracloud.org/coprs/djotaku/i3wm/packages/), but each > one had one or more dependencies. So I was rapidly along a path towards > having to recreate nearly all of Perl for EPEL8. (Only a slight > exaggeration). Unfortunately, for those, I couldn't just bum the spec file > because they each had a patch that needed to be applied. So I had to > download the repo from pagure, use spectool and mock to create the srpm and > then load that into copr. Quite tedious. > > However, the good news is that I never had to make any mods to the spec > files to get them to work for EPEL8. Everything just worked. So...what is > the proper path to get the perl folks to create epel8 branches in their > repos (again, there isn't any additional work needed - at least at this > point in time)? In the long run, I'd definitely like to be a co-maintainer > for i3 for epel8. I'll be pretty blunt here: I don't really care about having i3 in epel8, so as long as you take care of the epel8 branch and any bugs that pop up: I'm more than happy to add you as a co-maintainer. Cheers, Dan signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: i3wm for EPEL8
Adding the i3 SIG to the loop, maybe is something achievable by us. Br, El mar., 19 may. 2020 a las 14:11, Paul Howarth () escribió: > On Tue, 19 May 2020 10:47:57 -0400 > Eric Mesa wrote: > > I noticed that the i3 window manager wasn't available in EPEL8. Before > > trying to go through the process of becoming a package maintainer I > > decided to try and run it via copr to see how much modification was > > needed. For EPEL8 (as opposed to 7) I was able to take the current > > spec file and, after creating an EPEL8 copr repo for xcb-util-xrm ( > > https://copr.fedorainfracloud.org/coprs/djotaku/xcb-util-xrm/), it > > would build. But it wouldn't install for it needed some perl > > packages. So I set about building those. You can see how far I got in > > ( https://copr.fedorainfracloud.org/coprs/djotaku/i3wm/packages/), > > but each one had one or more dependencies. So I was rapidly along a > > path towards having to recreate nearly all of Perl for EPEL8. (Only a > > slight exaggeration). Unfortunately, for those, I couldn't just bum > > the spec file because they each had a patch that needed to be > > applied. So I had to download the repo from pagure, use spectool and > > mock to create the srpm and then load that into copr. Quite tedious. > > Interesting what you say about the perl modules because > perl-common-sense, perl-JSON-XS and perl-Types-Serialiser are available > in the EL-8 Code Ready Builder / PowerTools repo, which is a dependency > of EPEL-8: > https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F > > Is that repo not enabled in your EPEL-8 configuration? > > Paul. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Eduard Lucena Móvil: +56962318010 GNU/Linux User #589060 Ubuntu User #8749 Fedora Marketing Representative ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: i3wm for EPEL8
On Tue, 19 May 2020 10:47:57 -0400 Eric Mesa wrote: > I noticed that the i3 window manager wasn't available in EPEL8. Before > trying to go through the process of becoming a package maintainer I > decided to try and run it via copr to see how much modification was > needed. For EPEL8 (as opposed to 7) I was able to take the current > spec file and, after creating an EPEL8 copr repo for xcb-util-xrm ( > https://copr.fedorainfracloud.org/coprs/djotaku/xcb-util-xrm/), it > would build. But it wouldn't install for it needed some perl > packages. So I set about building those. You can see how far I got in > ( https://copr.fedorainfracloud.org/coprs/djotaku/i3wm/packages/), > but each one had one or more dependencies. So I was rapidly along a > path towards having to recreate nearly all of Perl for EPEL8. (Only a > slight exaggeration). Unfortunately, for those, I couldn't just bum > the spec file because they each had a patch that needed to be > applied. So I had to download the repo from pagure, use spectool and > mock to create the srpm and then load that into copr. Quite tedious. Interesting what you say about the perl modules because perl-common-sense, perl-JSON-XS and perl-Types-Serialiser are available in the EL-8 Code Ready Builder / PowerTools repo, which is a dependency of EPEL-8: https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F Is that repo not enabled in your EPEL-8 configuration? Paul. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
