Broken package

2023-05-09 Thread paul.mirkwood
h upstream has fixed the bug. The mangohud-git package is also fine. Best regards, and thanks for your answers, Mirkwood --- Forwarded Message --- De : paul.mirkwood Date : mardi 9 mai 2023 à 10:51 PM Objet : Broken package À : aur-general@lists.archlinux.org > Hello everyone, >

Re: Broken Package

2023-05-09 Thread paul.mirkwood
Thanks artafinde for the clarification, and thanks also Polarian, your explanations were worth reading! > As an additional sidenode, if the issue you want to report is that the > package is > broken because it can't be built, the maintainer has already highlighted that > it is due > to gcc updat

Re: Conflicting go package naming

2023-06-18 Thread paul.mirkwood
Hello, > "C" is just a letter of the alphabet ;), much likely nobody using Arch > Linux does confuse the letter of the alphabet with the programming > language, hence we don't call it "clang". I'm not convinced that "Go" > is a verb. Maybe it's an "abbreviation". It's probably both in one. > > Ou

Re: Conflicting go package naming

2023-06-18 Thread paul.mirkwood
Hello, > Is there a rational for naming packages "golang-golang-"* ? I don't know whether it's a good reason, but there's definitely a reason. There are basically two kinds of Go packages with a golang-* prefix in the official (non-AUR) Arch repos: - golang-golang-x-* packages, whose Upstream URL