Hello, For libraries you can include them in the package without any issues, but something else which is common in the official repositories is splitting it into libwiringx-git and have wiringx-git depend on it. This is usually done in split packages. This is because the shared object and headers are used for linking, and pulling an entire software package within a build environment is unnecessary. This is done on a package to package basis, but take sqlite [1] for example. The main command line utility and the library is provided by the sqlite package, but the parser and analyser is split out of the main package. Its however you feel it should be structured, if you want to split it up thats up to you, but seen as the program seems pretty small in size, and the library is tiny, I doubt it would make much of a difference in this case.
We may also want to include the static library. Thoughts?
The nature of static linking is for portability, and although reading about it there is some use cases for static libraries [2], most programs which static link will compile the program from source by default. Secondly this is slightly out of the scope of Arch Linux. Unless it is Rust or Go in which static linking is used by default, almost all software I have found written in C was dynamically linked, because there is little reason not to. The one big benefit of static linking is that it is a single executable, but when you have a package manager dealing with the libraries, it becomes redundant. Plus, if everything was static linked, you would have hundreds and hundreds of duplicate references to libraries included within the executable. Also another issue is the need for recompiling to update libraries which are out of date/vulnerable, although Arch Linux already will do this in a lot of cases, if the ABI remains constant, if a dynamic library is updated, anything linked against it will continue to work. (The big if there is the ABI remaining constant :P) I am not a staff member, and thus I do not know their procedures on rebuilds, but including a static library would only be useful if you were building statically linked software, and on Arch Linux, I doubt this is the standard (couldn't find any citation for this, if someone has a link to static vs dynamic discussions from staff, please send it). Hope this helps. Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev [1] https://archlinux.org/packages/core/x86_64/sqlite/ [2] https://en.wikipedia.org/wiki/Static_library