On Wed, Mar 25, 2020, at 1:18 PM, Vít Ondruch wrote: > > Dne 25. 03. 20 v 18:06 Vít Ondruch napsal(a): > > Dne 25. 03. 20 v 17:33 Aleksandra Fedorova napsal(a): > >> [snip] > >> We can come up with guidelines, for example: > >> > >> 1) Try to find a way to resolve the issue without any conditionals first. > >> > >> There should be a reason why package X needs a dependency Y in Fedora > >> and there should be a reason why it is a required dependency and not a > >> recommended one. So why in that case downstream wants it differently? > >> The first approach is just to talk through it. I can assume cases > >> where downstream adds a dependency, as well as Fedora package removing > >> them. > >> > >> Note that bloated dependency trees is a common problem for all binary > >> distributions, it is not an "EL-thing" and we can work on that > >> together. > >> > >> Nicolas has pointed out to another reason why we would get > >> EL-conditionals: the outdated rpm stack in RHEL. But we don't have > >> this problem with ELN, as we are building Rawhide, and rpm stack is > >> going to be the Rawhide rpm stack as well. > >> > >> 2) Minimize and isolate the conditional, and track the reason. > >> > >> As ELN SIG we need to have a place where we collect known reasons for > >> such conditionals. The overall goal is to reduce this set, not to grow > >> indefinitely. As Stephen said we expect it to be about couple of > >> hundred packages. We will be able to track each one of them. (We have > >> rpminspect to run package diffs for us). > >> > >> 3) In complex cases - bring it to community and FESCo. > >> > >> We don't know what those complex cases might be, one of the goals is > >> to find them. So we keep it as an option to bring individual case to a > >> wider audience. To ask for help and to decide on it. > >> > > It seems there are missing real life examples of what we sometimes do in > > RHEL, so please see attached patch. This patch is coming from RHEL > > version of the espeak-ng. Now somebody tell me what it does for what > > purpose and which scenario from the above three should be applied here. > > > > > > Vít > > > > And here is another example for the curious. > Both of these examples have to do with docs generation and trying to reduce dependencies for that process. "Process the man page using kramdown and remove the ronn dependency." (So you don't have to open the attachments yourself.) V/r, James Cassell _______________________________________________ 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
