| 2 Dec 2023 |
 mao_tse-tung | Hi hi!! Does anyone else have an interest in trying to package the latest (non-snapcraft) version of Spotify? | 04:40:28 |
| 3 Dec 2023 |
 symys | Interest? Yes? Follow-through? Probably not. Nix skills? Lmao 🤡 (that's me) | 03:04:02 |
| symys | * Interest? Yes. Follow-through? Probably not. Nix skills? Lmao 🤡 (that's me) | 03:04:14 |
| symys | In all seriousness, I'd be willing to help, but just know that it would be my first true packaging project. | 03:08:13 |
 Guillaume Desforges | Worry not, the nix community is helpful | 09:27:07 |
| Guillaume Desforges | You can ask questions in #dev:nixos.org for instance | 09:28:00 |
| Guillaume Desforges | But nobody will do the work for you ;) | 09:28:24 |
|  hopland (meticulous montesquieu) changed their display name from hopland (valorent vicky) to hopland (meticulous montesquieu). | 14:08:35 |
|  Sporesirius joined the room. | 22:31:31 |
| 4 Dec 2023 |
|  Jack joined the room. | 03:20:13 |
| 5 Dec 2023 |
|  Federico Damián Schonborn changed their profile picture. | 00:39:07 |
| symys | Spotify isn't open source though. Is it really compatible with nix packaging? | 13:10:13 |
 Minijackson | there is quite a number of non open-source software packaged in nixpkgs | 13:10:56 |
| Minijackson | if for example spotify is distributed as a flatpak app, there are functions to handle that | 13:11:24 |
| symys | Wait, also it is open source now | 13:11:33 |
| Minijackson | steam, as another example, constructs a whole "chroot" to make it happy | 13:11:50 |
| Minijackson | In reply to @fractivore:cyberia.club
Wait, also it is open source now even better :D | 13:11:54 |
| symys | Wait, nooo, they just have open sourced components of the platform. | 13:13:38 |
| Guillaume Desforges | In reply to @fractivore:cyberia.club
Wait, also it is open source now Wait wat | 13:26:50 |
| Guillaume Desforges | In reply to @fractivore:cyberia.club
Wait, nooo, they just have open sourced components of the platform. You got me there for a second | 13:27:18 |
| symys | So spotify is already packaged, but it's the snapcraft version? https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/applications/audio/spotify/linux.nix | 19:02:23 |
| symys | I don't really see why we need to repackage it without snapcraft | 19:02:48 |
| symys | Also spotify requires a specific minor version of openssl?? lool that doesn't seem great right? | 19:04:17 |
| symys | It looks like they worked around it by linking the system openssl version to a file named like the one spotify is expecting. | 19:05:45 |
| Guillaume Desforges | In reply to @fractivore:cyberia.club
It looks like they worked around it by linking the system openssl version to a file named like the one spotify is expecting. That's my jam | 19:21:45 |
| symys | It's a pretty cool hack yeah. | 21:40:51 |
| 7 Dec 2023 |
| Sporesirius | Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:
environment.systemPackages = with pkgs; [
r2305.alsa-lib
r2305.alsa-ucm-conf
r2305.alsa-utils
...
];
Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.
| 21:04:34 |
| Sporesirius | * Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:
environment.systemPackages = with pkgs; \[
r2305.alsa-lib
r2305.alsa-ucm-conf
r2305.alsa-utils
...
];
Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.
| 21:04:47 |
| Sporesirius | * Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:
environment.systemPackages = with pkgs; \[
r2305.alsa-lib
r2305.alsa-ucm-conf
r2305.alsa-utils
...
];
Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.
| 21:05:04 |
| Sporesirius | * Hi, I quite new to NixOS. I have a DAC where the latest version (1.2.10) of alsa-ucm-conf has a bug, because I'm on nixpkgs unstable I thought to add another input nixpkgs 23.05, so I can install an older alsa version.
So e.g:
environment.systemPackages = with pkgs; [
r2305.alsa-lib
r2305.alsa-ucm-conf
r2305.alsa-utils
...
];
Now, when I check what is installed, I have alsa-ucm-conf 1.2.10, 1.2.9 and alsa-lib 1.2.9, 1.2.8 installed, but each application still seems to reference alsa-lib 1.2.9, which in turn references alsa-ucm-conf 1.2.10.
| 21:05:38 |
