On Wed, Aug 17, 2022 at 02:25:06PM +0200, Lukas Javorsky wrote: > The Fedora change for this topic is created [1]. > > [1] https://fedoraproject.org/wiki/PcreRetirement It would be helpful to have an actual deadline written in there. "Fedora 39" requires an indirection. Are we talking 2023? 2024? What date exactly? I need to tell upstreams that they have until a certain date to make the change. Rich. > On Mon, Aug 15, 2022 at 11:46 AM Lukas Javorsky <ljavorsk@xxxxxxxxxx> wrote: > > Hi, > > I've decided to write a Fedora change that will contain all of the > information about this possible retirement. > > I have to fill the dependencies that will be affected by this change, so > I'm looking for the tool/command which will give them to me. > I've seen multiple suggestions here in this thread, but is there some kind > of consensus about which one should I choose (which one is the most > accurate)? > > Thank you so much > Lukas > > On Tue, Jul 26, 2022 at 11:17 AM Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > Due to static linking, not all functions will be included in the > executable and therefore some simple "hello world" binaries will not > need sysprof-capture-static. However, anything that used the .pc file > will need it. > > Technically, you could also use glib's static library without dependent > .a libraries if you link with glib's .a file but do not specify > -static; but that's not a good argument against having a Requires for > the dependency in my opinion, because it makes the .pc file not work > out of the box. Perhaps a weak dependency, but even that sounds > strange. > > As to glibc-static I think it's fair to say that whoever uses -static > will have to install it on their own, so it can be left out of > glib2.spec. > > Paolo > > > Il mar 26 lug 2022, 10:59 Daniel P. Berrangé <berrange@xxxxxxxxxx> ha > scritto: > > Although listed in glib-2.0.pc, I didn't find any need for the > sysprof-capture-static package, but it does need glibc-static > > _______________________________________________ > 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 > > > > -- > S pozdravom/ Best regards > > Lukáš Javorský > > Software Engineer, Core service - Databases > > Red Hat > > Purkyňova 115 (TPB-C) > > 612 00 Brno - Královo Pole > > ljavorsk@xxxxxxxxxx > > [logo--200] > > > > > > -- > S pozdravom/ Best regards > > Lukáš Javorský > > Software Engineer, Core service - Databases > > Red Hat > > Purkyňova 115 (TPB-C) > > 612 00 Brno - Královo Pole > > ljavorsk@xxxxxxxxxx > > [logo--200] > > -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
