Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#63368 - [vim] different code producing binaries of the same name in the same PKGBUILD

Attached to Project: Arch Linux
Opened by lilydjwg (lilydjwg) - Monday, 05 August 2019, 04:00 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 05 August 2019, 04:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



It will produce broken debug packages in this way.

Yes I know requesting something without any useful technical change is no good. But I didn't know how to improve the situation. The only information I got previously was that way in PKGBUILD is poor, so I was asking a better way.

Eli Schwartz suggests in the gvim package you can symlink gvim to vim instead. Could you consider and make the change? Or do you have a better solution like making it two PKGBUILDs? (But I'm not sure how to split it to two while it produces three packages.)

Anyway, I'm not insulting anyone. I'm seeking for a recommended PKGBUILD for vim that will not break when producing debug packages.

I constantly refer to official PKGBUILDs for my own packages to avoid poor or broken packages that causes headaches sooner or later.
This task depends upon

Comment by Eli Schwartz (eschwartz) - Monday, 05 August 2019, 04:37 GMT
ref: as per FS#63366, a PKGBUILD that packages different code to the same path in different components of a split package, for example the vim binary which is present in both "vim" and "gvim", will (in an upcoming version of pacman/makepkg) trigger a warning while stripping detached debug symbols.
Comment by lilydjwg (lilydjwg) - Monday, 05 August 2019, 06:27 GMT
Thanks. That sounds good.

I've hacked my own version of PKGBUILD to not only symlink gvim / vim the other direction, but also avoid the duplication of source files. And it seems to work. (I still don't know what .build-id files are there for, but it doesn't matter.)

You may close this task now.