Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
add architecture specific dependency fields support #465
Currently, the RPC interface doesn't support architecture specific fields. It merges them in the generic arrays instead. See FS#48796.
Partial support for arch specific dependencies has been implemented with a temporary workaround in 6e3cb3b. This will however work only if the 32 bits (make)dependencies use the naming prefix
It is possible to implement another temporary hack by reading and parsing the .SRCINFO files to retrieve the correct information. This indeed bypasses the RPC interface, and is implemented by bauerbill and pkgbuilder. This would however require to substantially change the current design as PKGBUILD cloning is done after dependency resolution, and this is something I'm not going to do. I will instead wait for the proper fix to be implemented in the RPC. Once this is done, correct arch specific support will be trivial to add and the existing hack can be removed.
I hope this is the same issue:
@rmarquis You got it wrong I think. Official i686 support in the repo from current devs is what is going out.
i686 will probably stay, the ideal goal being to have it built in an automated manner by the end of the year. But what is sure, is that support for multiple architectures will stay in all the tools.
That being said, I’m not asking you to spend any of your time on this issue until at least the future of i686 is established. ;)