Re: Package Maintainer Application - Carl Smedstad
On Sun, Mar 03, 2024 at 03:27:54PM +, Carl Smedstad wrote: > Hi everyone, Yo! > [] > > For reference, PKGBUILDs for all packages I maintain in the AUR are > available here: https://github.com/carlsmedstad/aurpkgs As of writing I have gone through ~100 of the ~160 available packages (skipping a few ruby ones) and generally the quality seems good. I notice you are using `-buildvcs=false` in some Go packages which should probably go into the package guidelines, but that is largely on me. > I've also published some helper scripts I use: > https://github.com/carlsmedstad/aurutils-extra Generally seems like high quality scripts. One nitpick is that you can replace all your `[ "$some_check" = 1 ];` with `((some_check))` which is less letter to type. I'd also maybe look at parsing .SRCINFO instead of sourcing PKGBUILD, but not super relevant for a TU application :) > For my other OSS-contributions, primarily bug reports and minor patches, > my GitHub profile is most likely the best place to get an overview. I went back a few years on Github and the bug reports seems to generally be of a nice and high quality. > Thank you for taking the time to read this, cheers! Thanks for applying and good luck. Now, excuse me. I need to find a Norwegian to sponsor as we can't have the swedish leading with 3 packagers. -- Morten Linderud PGP: 9C02FF419FECBE16 signature.asc Description: PGP signature
Re: Migration of p7-tools to cahute
On Mon, 11 Mar 2024 15:43:23 + "Eldeberen" wrote: > - How do I manage the decommissioning of the old tools? You request that they be merged into the new package. Anyone that has notifications set should get an email. > - I understand I'm not allowed to use the 'replaces' directive on the > PKGBUILD as it is not an official package, I am right? You can, it just won't do much in the AUR. It's generally advised against because people don't understand when to use it, but this is exactly the type of case it was made for. Unfortunately, replaces only does anything when the package is in a pacman repo, and won't do anything when people just -U the package. People managing a local repo will get an automatic replacement instead of having to `pacman -Syu cahute`, so there's that, but that's about it. > - Should I add some warnings on existing p7/libp7/p7screen packages warning > that they are no more maintained? Merging should take care of that.
Re: Migration of p7-tools to cahute
Ey, Does installing cahute and removing the other packages break existing files? If not, you should be able to use replaces. Cheers, Aᴀʀᴏɴ
Migration of p7-tools to cahute
Hi everyone, I currently maintain some packages on the AUR, related to Casio calculators. In particular we'll focus on p7/libp7/p7screen which are dedicated to communication protocols. https://aur.archlinux.org/packages/p7 https://aur.archlinux.org/packages/libp7 https://aur.archlinux.org/packages/p7screen Recently the developer (Cakeisalie5) rewrote these utilities and replaced them by a single package, Cahute. https://cahuteproject.org/ I made a new package for this, which is not yet on the AUR but can be found on my personnal forge: https://git.middleearth.fr/Packages/cahute So I have some questions for you ^^ - How do I manage the decommissioning of the old tools? - I understand I'm not allowed to use the 'replaces' directive on the PKGBUILD as it is not an official package, I am right? - Should I add some warnings on existing p7/libp7/p7screen packages warning that they are no more maintained? - On the cahute package, does the .install looks good? - More generally I'll take any advise that help me to comply with the AUR guidelines :) Thanks for your help, Eldeberen
