The latter change seems unwise. Packages which now depend on minizip (to be minizip-ng)
will continue to do depend on whatever Provides(minizip); if you rename the zlib
subpackage to minizip, they will depend on the wrong thing.
Cheers,
Marcus
On 28.07.22 10:31, Lukas Javorsky wrote:
Hi fellow contributors,
Upstream has reported a request for minizip naming change from "minizip" to "minizip-ng"
(minizip-ng is the official name of the upstream package right now).
As Fedora should match the upstream naming, I believe this change is necessary.
Another naming change is required for the "minizip-compat" package which is the
subpackage of the "zlib" package. Upstream requests that we should rename
"minizip-compat" to "minizip".
I agree with renaming this package as well, however, this could lead to multiple
confusions maybe even conflicts for the users. The problem with renaming this package
right after renaming the "minizip-ng" could be that the users may be confused about
which package is the right "minizip" for them.
I believe we could rename the "minizip-compat" to the "minizip" after some larger time
period so every package that requires "minizip" changes the requirements to "minizip-ng"
and there is no confusion anymore.
The first step I want to do is to create a Fedora Change, which contains this whole
process and is well communicated within the community.
This email serves as a heads-up and also opens a possibility for any tips that you can
give me with this change. This is my first time doing a change like this so it may have
some bumps along the way, but I'm willing to learn and improve, so feel free to give me
any advice you think could benefit me with this process.
Thank you for understanding and sorry for quite a long email.
Lukas
--
S pozdravom/ Best regards
Lukáš Javorský
Software Engineer, Core service - Databases
Red Hat <https://www.redhat.com>
Purkyňova 115 (TPB-C)
612 00 Brno - Královo Pole
ljavorsk@xxxxxxxxxx
<https://www.redhat.com>
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
