You are not logged in.
I'm trying to submit and maintain various cross compiler packages for Free Pascal. However, even though each can build just fine, they each generate a ppcrossXXX binary, where XXX would be the suffix for the CPU (ie. '386' for i386, or 'x64' for x86_64). This was fine at first, but then I tried making a cross compile package for i386-freebsd when I already had i386-win32. Both generate ppcross386, and it ends up as a file conflict upon trying to install, even though ppcross386 can work for both targets.
I unfortunately cannot build ppcross386 as its own package and have those two depend on it. If I code in the PKGBUILD to check for existence of ppcross386, it will likely detect an older version upon a future update of the package, not just one provided by another package.
I do have an idea, however. Can I code into my PKGBUILDs the ability to check for the existence of an installed package and take a conditional action depending on its presence? All I can think of is the confliction ability, which isn't good because these packages need to be able to coexist, with an exception to this one file. Something like is_pkg_installed('fpc-cross-i386-win32'), so that such a function call can be placed in an 'if' clause or something.
EDIT: Nevermind, I found a solution. Feel free to delete this topic.
Last edited by Schala (2012-03-08 17:41:46)
Hardware: Gigabyte X570 AORUS Pro, AMD Ryzen 5900X, Nvidia GTX 1080, 32 GB DDR4 RAM
Choice software: Arch Linux 64-bit with KDE desktop / Windows 11 Home 64-bit
Offline