> As per Changes/GolangPackagesVendoredByDefault [1], all golang libraries > that are currently leaves (as defined in [2]) will be mass retired. This > will happen in the coming days. The full list of packages is available at > [3]. I am glad to see this. The vendored-dependency approach has made my maintenance of Fedora's Hugo package much easier. Gone is the dread that each version of Hugo will require multiple package reviews of new Go dependencies. Thank you!
Yet I do worry about some packages. The golang-modernc series, for example, has a number of idiosyncrasies that I would not want each application packager to have to relearn. Is there a way to establish exceptions to the leaf-implies-retirement rule? Is there a way for an otherwise vendored-dependency application to make use of external Go packages when there are exceptional circumstances? -- Mike :wq -- _______________________________________________ devel 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, report it: https://pagure.io/fedora-infrastructure/new_issue
