On 03/05/2019 17:23, Bruno Pagani via aur-general wrote: > Le 03/05/2019 à 16:04, Eli Schwartz via aur-general a écrit : > >> Furthermore, I defy the idea that even users building it themselves >> constitute "user stupidity", because as Lone Wolf's explanation >> *explicitly* called out, it is awkward in the extreme to kludge around >> adding a *build-time* codegen dependency on llvm-git, inside a >> makechrootpkg compilation environment... without actually doing so via >> makepkg's "makedepends" technology. > I did not understood that paragraph. It refers to the email from Lone_Wolf that proposed an env variable that will at build time generate/manipulate deps by inspecting the system. > > Bruno
I am a bit baffled by this thread. I understand we have standards and requirements and suggestions and best practices and so on, but for the Arch User Repository - is Lone_Wolf not allowed to make a package called 'my-awesome-mesa-git-that-uses-llvm-git-and-thats-final'? And as long as it builds, installs safe, runs fine, **fulfils a purpose**, **doesn't have an equivalent** and **does not abuse the website or users**, then all we can do is say 'Good Job'? This is both a genuine question and a personal surprise if it is otherwise. As for the general **good** way of doing this, we already know to do it - we either have a single person in charge of the whole stack and each release is binary consistent or we communicate and sync our builds/releases. Why not just make sure/trust Lone_Wolf that they will do their part as maintainer and check for all dependencies and provide version bumps and prompt updates, etc as any good maintainer will? Regards, Konstantin
signature.asc
Description: OpenPGP digital signature
