https://bugzilla.redhat.com/show_bug.cgi?id=1970619
--- Comment #4 from Major Hayden 🤠<[email protected]> --- (In reply to Ben Beasley from comment #3) > One way to avoid pulling in the full contents of this (admittedly small > package) to create a directory would be to create a -filesystem package; > that seems overkill for only one directory. So Azure has some remnants in their SDK repository that are meant to do that for Python versions before 3.0: ➜ find . -name "*-nspkg" ./sdk/nspkg/azure-agrifood-nspkg ./sdk/nspkg/azure-ai-nspkg ./sdk/nspkg/azure-ai-translation-nspkg ./sdk/nspkg/azure-cognitiveservices-knowledge-nspkg ./sdk/nspkg/azure-cognitiveservices-language-nspkg ./sdk/nspkg/azure-cognitiveservices-nspkg ./sdk/nspkg/azure-cognitiveservices-search-nspkg ./sdk/nspkg/azure-cognitiveservices-vision-nspkg ./sdk/nspkg/azure-communication-nspkg ./sdk/nspkg/azure-data-nspkg ./sdk/nspkg/azure-digitaltwins-nspkg ./sdk/nspkg/azure-iot-nspkg ./sdk/nspkg/azure-keyvault-nspkg ./sdk/nspkg/azure-media-nspkg ./sdk/nspkg/azure-messaging-nspkg ./sdk/nspkg/azure-mgmt-datalake-nspkg ./sdk/nspkg/azure-mgmt-nspkg ./sdk/nspkg/azure-mixedreality-nspkg ./sdk/nspkg/azure-nspkg ./sdk/nspkg/azure-purview-nspkg ./sdk/nspkg/azure-search-nspkg ./sdk/nspkg/azure-security-nspkg ./sdk/nspkg/azure-storage-nspkg ./sdk/nspkg/azure-synapse-nspkg ./sdk/nspkg/azure-monitor-nspkg From what I can see in most of the requirements code, they don't use it much anymore. ":python_version<'3.0'": ['azure-mgmt-nspkg'], > I think the approach of co-owning any namespace directories would work well > here. That ought to just need this added: > > > # Co-owned namespace package directory > > %dir %{python3_sitelib}/azure > > in the %files section of every package that installs something directly into > the azure directory. This makes sense to me. There's going to be quite a few things that install into %{python3_sitelib}/azure/** and it's not a big deal to add that to each spec. I'll adjust it and submit a new spec. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
