activitywatch: init at 0.12.1

[chaoky]

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[chaoky]

maybe this should be called activitywatch-bin? as there is some effort to create a compiled version in #97379

[auroraanna]

maybe this should be called activitywatch-bin? as there is some effort to create a compiled version in #97379

nixpkgs only appends -bin on some package's name whose package can't be built from source. nixpkgs tries to make stuff build from source where ever possible and then Hydra builds it and puts it on cache.nixos.org. That cache will then contain the built package with the binary executable.

So, if there is already a version compiled from source, then a -bin one would be unnescessary.

[chaoky]

Thanks for taking the time to clarify, so should this just be kept as activitywatch?
~ and updated with a compiled version when (and if) it's ever packaged from source

my question came from seeing a lot of foo-bin oss packages on nixpkgs
aur builds are also compiled and cache

[auroraanna]

Hmm, I'm not so sure anymore it it's unnescessary. wkhtmltopdf and wkhtmltopdf-bin exist in nixpkgs, same for Thunderbird.

[amz-x]

I'm also interested in this package.

I do agree with @chaoky to rename it to activitywatch-bin, since the compiled version in #97379 would be activitywatch thus keeping the package naming convention consistent.

[unode]

@chaoky this recipe doesn't seem to work for me.
None of the bundled binaries have been patched.
They all still expect /lib64/ld-linux-x86-64.so.2 to be the interpreter.

% file /nix/store/9cvi0pxc2dibqjsmryd5baz279888gc4-ActivityWatch-0.12.1/opt/activitywatch/aw-qt 
/nix/store/9cvi0pxc2dibqjsmryd5baz279888gc4-ActivityWatch-0.12.1/opt/activitywatch/aw-qt: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9230f3fa19123436d7e9b46b02c11f1e492895c1, for GNU/Linux 2.6.32, stripped

% ./.nix-profile/bin/aw-qt 
zsh: no such file or directory: ./.nix-profile/bin/aw-qt

Did you do something else to have this recipe running in your system?

[chaoky]

@chaoky this recipe doesn't seem to work for me. None of the bundled binaries have been patched. They all still expect /lib64/ld-linux-x86-64.so.2 to be the interpreter.

% file /nix/store/9cvi0pxc2dibqjsmryd5baz279888gc4-ActivityWatch-0.12.1/opt/activitywatch/aw-qt 
/nix/store/9cvi0pxc2dibqjsmryd5baz279888gc4-ActivityWatch-0.12.1/opt/activitywatch/aw-qt: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=9230f3fa19123436d7e9b46b02c11f1e492895c1, for GNU/Linux 2.6.32, stripped

% ./.nix-profile/bin/aw-qt 
zsh: no such file or directory: ./.nix-profile/bin/aw-qt

Did you do something else to have this recipe running in your system?

It's wrapped now, the autoPatchelfHook is only there to pick up libz.so.1, I couldn't figure out how to include this library otherwise

[chaoky]

I see these on the runtime logs

/nix/store/8jlrffqj4h476lmd42l3flrpcl6z2813-ActivityWatch-0.12.1/opt/activitywatch/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /nix/store/3ph4rh9id7an858r1p7dj90nhf78g7s0-libproxy-0.4.18/lib/libproxy.so.1)

I'm not sure weather this is a non-nixos issue, or how to fix it, if it isn't it.
This comes from glib-networking, which is not essential for this package.

[SuperSandro2000]

Please follow the contributing guide when naming your commits.

[SuperSandro2000]

Why not compile from source?

[chaoky]

activitywatch is composed of a lot of small services, the derivation proposed in the related issue is 380 lines long

[SuperSandro2000]

which is preferable if someone already has done the work

[chaoky]

I'll try, what do you recommend for node packages? buildNpmPackage?

[SuperSandro2000]

@ofborg eval

[unode]

Superseded by #202935