Re: Package Maintainer application - Bert Peters
On 05.05.24 at 14:18 (UTC+0200), Bert Peters wrote: > Hi all, > > My name is Bert Peters, or bertptrs on IRC and various other places, > and I'm applying to become a package maintainer for Arch Linux. My > application is sponsored by Christian Heusel (gromit) and Jakub > Klinkovský (lahwaacz). > Hi, I hereby confirm my sponsorship of Bert's application. Good luck! Cheers, Jakub signature.asc Description: PGP signature
Re: wiringX-git PKGBUILD Review Request
You might also want to look at the CMake package guidelines [1]. In particular, cmake should be called from build(), not prepare(). [1] https://wiki.archlinux.org/title/CMake_package_guidelines signature.asc Description: PGP signature
Re: Application to become a package maintainer
On 14.11.23 at 13:44 (UTC+0100), Robin Candau wrote: > Le 12/11/2023 à 23:34, Jakub Klinkovský a écrit : > > First, I think it is fair to acknowledge that I do not plan to deal with > > handling AUR requests, which is still associated to the role of a package > > maintainer. Dealing with the wiki is hard and time consuming in itself and I > > don't have the capacity to add another similarly exhausting responsibility. > > > Fair enough. As Torsten said, hopefully this will be handled by the (soon to > be) AUR moderators role at some point :) Thanks for understanding. I think it would be very helpful to have the expectations and responsibilities clearly separated between these two roles. > I had a quick look at your PKGBUILDs and they all look really great! > > If I had to raise a few things, just for the sake of it, I would eventually > raise that: > - You don't explicitly have to `cd` to "$srcdir" during the `mythes-cs`'s > package function [1] as functions are already executed from that directory > by default. > - The "v" prefix of the `oojs-ui-archlinux-git`'s tags should be cut off the > pkgver [2]. You can adapt the `pkgver()` function accordingly, as described > in the VCS packaging guidelines [3]. You have hawk eyes! I just fixed both issues and took the opportunity to upgrade oojs-ui-archlinux to v0.48.2. Best regards, Jakub signature.asc Description: PGP signature
Re: Application to become a package maintainer
On 13.11.23 at 8:56 (UTC+0100), Torsten Keßler wrote: > Hey Jakub, > > I'm excited to see your application as a package maintainer! As we discussed > in the chat a while ago, we always need help in maintaining HPC/ML packages. Thanks! I will gladly offer my hands and hardware to help. > I did a review of your packages. High quality PKGBUILDs for important HPC > libraries. Even with ROCm support. Very nice! > One small remark: Package guidelines discourage the use of > CMAKE_BUILD_TYPE=Release (see tnl-git and pastix). Right, thanks for the note. I fixed it easily for pastix and it should also be fine for ginkgo-git, though I will need to check if some other issues popped up since the last time I built it from the develop branch... Which reminds me that I should also enable ROCm support in Ginkgo :-) For tnl-git, there is actually a difference between the Release and None build types, since the project adds the -O3 -DNDEBUG flags for the Release build. The -O3 may be arguably unnecessary, but omitting the -DNDEBUG would make the binaries veeery slooow. I could add -DNDEBUG to CXXFLAGS manually, but I'm not sure if that is better than CMAKE_BUILD_TYPE=Release. I should also disclose that I'm an upstream developer of this TNL project. This is where I find all the bugs in the nvcc compiler :-D Jakub signature.asc Description: PGP signature
Application to become a package maintainer
Hey everyone, I'm sending my application to become a package maintainer, which is kindly sponsored by Sven (svenstaro) and Frederik (freswa). ## Who I am My name is Jakub, but I'm mostly known as Lahwaacz online. I've been an Arch wiki admin since 2014 and also created the man.archlinux.org project. In real life, I have scientific background and I'm interested in programming, automation and infrastructure. I write Python, C++ and CUDA (no Rust yet :-(). ## What I want to do I want to help with package maintenance in two general areas that are closest to me: 1. Due to my background, I'm using many weird scientific packages (almost) daily, including cuda, openmpi, vtk, paraview and more. Most of these are notorious for breaking often and I'd have to deal with this anyway, so I might as well directly co-maintain them. 2. As a wiki admin I could co-maintain some wiki-related packages, both for users and for backend deployment. The Arch wiki is based on MediaWiki which is currently deployed from a single git mono-repository that contains all necessary extensions (either bundled or as git submodules) but we would like to eventually use Arch packages for MediaWiki and its extensions. This is a long-term goal for me, however, since I have yet to learn how to do PHP packaging properly... I may find also other areas where to invest my packaging time, but overall I imagine myself maintaining a small-ish number of packages and focusing on quality rather than quantity. ## Disclaimers First, I think it is fair to acknowledge that I do not plan to deal with handling AUR requests, which is still associated to the role of a package maintainer. Dealing with the wiki is hard and time consuming in itself and I don't have the capacity to add another similarly exhausting responsibility. I like Python as a language, but I dislike Python packaging and I don't see myself maintaining many Python packages in the future. I might change my opinion, though, since I would really love to see jupyterhub in the official repos: https://aur.archlinux.org/packages/jupyterhub ## My packages My AUR packages: https://aur.archlinux.org/packages?SeB=m=lahwaacz I also maintain an unofficial [jlk] repo which contains many other AUR packages that I use: https://jlk.fjfi.cvut.cz/arch/repo.html Feel free to bombard me with any questions or package reviews :-) Best regards, Jakub / Lahwaacz signature.asc Description: PGP signature
