https://bugzilla.redhat.com/show_bug.cgi?id=2344534
--- Comment #11 from wojnilowicz lukasz.wojnilowicz@gmail.com --- (In reply to Fabio Valentini from comment #10)
Some problems with associating spec parts with the correct subpackage:
Requires: aw-server-rust
and
# Hopefuly one day it will be a part of aw-server-rust # https://github.com/ActivityWatch/activitywatch/issues/92#issuecomment-158393... Provides: bundled(aw-server-rust)
and all of:
%post %systemd_user_post %{watcher_name}.service %preun %systemd_user_preun %{watcher_name}.service %postun %systemd_user_postun_with_restart %{watcher_name}.service
These all need to be associated with the "aw-awatcher" subpackage, otherwise they won't have any effect.
Done.
I wonder if it could make sense to just name the "source" package "aw-awatcher" instead? That would let you avoid this kind of issue.
The project is named awatcher though, and I feel comfortable with that name. That would avoid this kind of issue, but wouldn't make me aware of it.
The project also provides a .desktop file, would you like to package that?
No. That would be needed if I would target for a bundle with aw-server-rust and would get an executable. I'm targeting for a non-executable plugin that would be loaded by aw-server-rust.
Could you approve now?
[fedora-review-service-build]