I'm packaging a module for xrdp that allows it to work with pipewire: https://build.opensuse.org/package/show/home:jacraig:xrdp/pipewire-module-xr... Any suggestions would be helpful. A specific question I have is I don't understand the documentation for %suse_update_desktop_file; am I doing this right? Also there is a warning for an unstripped binary (the .so file), saying "this is normally done by RPM at build time". Why isn't it being done? And am I right that I don't worry about a SONAME because it is a plugin? thanks /Jason Craig
Hello Jason, Am Freitag, 18. August 2023, 01:18:44 BST schrieb Jason Craig:
I'm packaging a module for xrdp that allows it to work with pipewire: https://build.opensuse.org/package/show/home:jacraig:xrdp/pipewire-module-xr...
Any suggestions would be helpful. A specific question I have is I don't understand the documentation for %suse_update_desktop_file; am I doing this right?
Looks good, but mae sure you have the .desktop file installed # menu-entry desktop-file-install --dir %{buildroot}%{_datadir}/applications %{name}.desktop %suse_update_desktop_file %{name} %{name} does not match the desire name in that case.... Maybe you check with the version in our spec file - autosetup with the full hash behind will probably required adjustment of this line each time the version changes HTH Axel
On 8/18/2023 2:16, Axel Braun wrote:
# menu-entry desktop-file-install --dir %{buildroot}%{_datadir}/applications %{name}.desktop %suse_update_desktop_file %{name}
%{name} does not match the desire name in that case....
I can't get this to work...I'm trying desktop-file-install --dir %{buildroot}%{_datadir}/applications pipewire-xrdp.desktop since that is the name of the desktop file (not the same as %{name} like you say) but build says "pipewire-xrdp.desktop": No such file or directory
Maybe you check with the version in our spec file - autosetup with the full hash behind will probably required adjustment of this line each time the version changes
I'm not sure I understand what you are saying here. If you're saying the git commit hash will have to change when new source comes out I understand that (there are no tagged version releases for the project yet). thanks /Jason Craig
Am 20. August 2023 00:08:17 GMT+01:00 schrieb Jason Craig
On 8/18/2023 2:16, Axel Braun wrote:
# menu-entry desktop-file-install --dir %{buildroot}%{_datadir}/applications %{name}.desktop %suse_update_desktop_file %{name}
%{name} does not match the desire name in that case....
I can't get this to work...I'm trying desktop-file-install --dir %{buildroot}%{_datadir}/applications pipewire-xrdp.desktop
since that is the name of the desktop file (not the same as %{name} like you say) but build says "pipewire-xrdp.desktop": No such file or directory
make sure you select the right source directory. the .desktop seems not to be in the root directory of your tarball
Maybe you check with the version in our spec file - autosetup with the full hash behind will probably required adjustment of this line each time the version changes
I'm not sure I understand what you are saying here. If you're saying the git commit hash will have to change when new source comes out I understand that (there are no tagged version releases for the project yet).
OBS has a source service for git, which manages this. I haven't used that for ages, so better look this up in the wiki HTH Axel
Do you know the site https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#.25suse_up...
Maybe the parameter -i or another one helps?
Regards
Eric
Am 20. August 2023 01:08:17 MESZ schrieb Jason Craig
On 8/18/2023 2:16, Axel Braun wrote:
# menu-entry desktop-file-install --dir %{buildroot}%{_datadir}/applications %{name}.desktop %suse_update_desktop_file %{name}
%{name} does not match the desire name in that case....
I can't get this to work...I'm trying desktop-file-install --dir %{buildroot}%{_datadir}/applications pipewire-xrdp.desktop
since that is the name of the desktop file (not the same as %{name} like you say) but build says "pipewire-xrdp.desktop": No such file or directory
Maybe you check with the version in our spec file - autosetup with the full hash behind will probably required adjustment of this line each time the version changes
I'm not sure I understand what you are saying here. If you're saying the git commit hash will have to change when new source comes out I understand that (there are no tagged version releases for the project yet).
thanks /Jason Craig
participants (4)
-
Axel Braun -
Axel Braun -
Eric Schirra -
Jason Craig