Le jeu. 7 mars 2024 à 13:28, Robin Candau <antiz@archlinux.org> a écrit :
On 3/7/24 13:21, Ryan Petris wrote:
On Thu, Mar 7, 2024, at 4:38 AM, Robin Candau wrote:
On 3/7/24 12:34, lacsaP Patatetom wrote:
hi, Hi,
when I run `makepkg`, it generates a second package with the `-debug` "extension" (eg. `mypackage-w.x.y-z-x86_64.pkg.tar.zst` and `mypackage-debug-w.x.y-z-x86_64.pkg.tar.zst`).
I couldn't find anything about this on the wiki : is this a new feature and/or is there a parameter to pass to `makepkg` to avoid building it ?
Debug packages have been introduced in Arch in early 2022. See https://archlinux.org/news/debug-packages-and-debuginfod/ <https://archlinux.org/news/debug-packages-and-debuginfod/>
regards, lacsaP.
-- Regards, Robin Candau / Antiz
*Attachments:*
* OpenPGP_0xFDC3040B92ACA748.asc * OpenPGP_signature.asc
Arch itself may have been generating debug packages since 2022, however it's only recently that makepkg started spitting out debug packages by default. The change was made all the way back in June of last year < https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a>, but was only included in a pacman release at the beginning of February < https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/tags/6.0.2-9>, as part of a pkgrel bump.
This came as a surprise to me as well, when I had -debug packages start showing up in my personal repository when they had not before, without any changes made on my end.
Personally I would have expected some sort of announcement for this change, though there was none. The news in 2022 said that enabling debug packages for all packages was an ongoing effort, suggesting that such a change would happen sooner or later. But fair enough, I get your point.
If anything, as Christian/gromit already said in a previous mail on that thread, you can disable the debug option in PKGBUILDs/makepkg.conf to avoid -debug packages from being created.
-- Regards, Robin Candau / Antiz
thank you for your answers. I did see the changes introduced last February in `/etc/makepkg.conf` but I had targeted those related to Rust since my package is "based" on cargo. have a nice day, regards, lacsaP.