FS#66888 - Debug package may conflict with the original
Attached to Project:
Pacman
Opened by Yichao Yu (yuyichao) - Thursday, 04 June 2020, 03:05 GMT
Last edited by Morten Linderud (Foxboron) - Monday, 02 May 2022, 14:06 GMT
Opened by Yichao Yu (yuyichao) - Thursday, 04 June 2020, 03:05 GMT
Last edited by Morten Linderud (Foxboron) - Monday, 02 May 2022, 14:06 GMT
|
Details
Summary and Info:
For some languages, for example julia, the julia source file could be part of the package but will also appear as source files in the compiled binary. When making a package with `(debug strip)`, the source files will be included in both the debug package and the original one causing a conflict. The obvious solution would be to detect and remove such conflicts though other solutions like specifying white/black list in PKGBUILD can also work in this case. Steps to Reproduce: |
This task depends upon
Closed by Morten Linderud (Foxboron)
Monday, 02 May 2022, 14:06 GMT
Reason for closing: Fixed
Additional comments about closing: ae2f506ddfd11d9becda7216033fe1b159536982
Monday, 02 May 2022, 14:06 GMT
Reason for closing: Fixed
Additional comments about closing: ae2f506ddfd11d9becda7216033fe1b159536982
(FWIW: packages producing debug sources in the build machine's ${srcdir} because they completely ignore CFLAGS are a pure and simple matter of an upstream bug, not a makepkg bug.)
To be clear, this applies to non-c/c++ source code. Julia is both the package and the language. The source file is installed as part of the package under `/usr/share/julia/`, which is also how they are referred to in the language and what saved to the library as the source path.
Actually, looking at this again, it seems that `makepkg` is actually picking up the files from the system installation when compiling out of a chroot. A clean chroot build might not actually have this problem. Nonetheless, I think the logic should make sure no files are copied from outside `$srcdir`. Those are almost certainly the wrong paths.