graphics::wayland::weston: make this a multipackage #127
Conversation
Weston provides a libweston, others may want to use.
| mesonPackageDev | ||
| installCopy "$1/install/" \ | ||
| "/usr/" "/usr/share/" \ | ||
| "/usr/share/libweston-14/" \ | ||
| "/usr/share/libweston-14/protocols/" |
There was a problem hiding this comment.
You can pass the additional paths directly to mesonPackageDev:
| mesonPackageDev | |
| installCopy "$1/install/" \ | |
| "/usr/" "/usr/share/" \ | |
| "/usr/share/libweston-14/" \ | |
| "/usr/share/libweston-14/protocols/" | |
| mesonPackageDev "$1" \ | |
| "/usr/" "/usr/share/" \ | |
| "/usr/share/libweston-*/" \ | |
| "/usr/share/libweston-*/protocols/" |
| provideDeps: [ "*-tgt" ] | ||
|
|
||
| provideDeps: [ "*-tgt" ] | ||
| dev: |
There was a problem hiding this comment.
I know we didn't do it in the past but should we start to name the libraries explicitly? Something along the following lines?
multiPackage:
"": # the weston binary
libweston:
multiPackage:
dev: ...
tgt: ....
I came across this in #125 where multiple libraries were provided.
@rhubert, do you have an opinion on this?
There was a problem hiding this comment.
This may make sense with something like systemd. I am not sure if this should be a general rule. Normally all libs of a package are required. Also in this case only one lib will be installed, so there is no need in naming it explicitly. Please, also keep in mind that this may make virtual packages harder, because the target naming scheme may not be predictable anymore.
2 participants
Weston provides a libweston, others may want to use.