I just found out that Bisq2 was released.
You know, the thing with Java applications is that building them from source using Nix is really difficult. During the development of the Nix package for Bisq, I wrote a script which I would run to generate a Nix expression describing the Java packages which needed to be downloaded. Then another Nix expression would create a temporary (Maven) repository containing the downloaded dependencies. THEN, it was possible to build Bisq with Nix.
But I ran into a problem: I needed to include some DAO data and there was no way to get that in a reproduceable way, causing the build to fail when the DAO data was updated by upstream. I did find a solution. It so happened that the upsteam Linux package included the DAO data. I realized that I could get the DAO data from that file, solving the reproduceability problem. But at that point I also realized that if I was going to have to download the upstream linux package to get the data I needed, why not just repackage upstream's package for NixOS? This is the reason why the current Nix Bisq package is a repackaging up upstream's package, rather than a source build.
I don't know why I'm saying all of this, other than perhaps I'm feeling uncharacteristically chatty today.
I'm going to take a look at Bisq2 and create a Nix package for it. I can guarantee that I won't be building it from source ;)
emmanuelrosa / Emmanuel
npub18e…ucvu7
2024-03-30 00:54:27
Author Public Key
npub18eynzyyrx0v46qjnvtj6mvekpxlfnkq06e3zfd6q9487vty0lfaszucvu7Published at
2024-03-30 00:54:27Event JSON
{
"id": "5d49191cf14b68f1f91fc2192bcb272d6aaaa9ab5656b53f862164b45a0c451e",
"pubkey": "3e4931108333d95d025362e5adb33609be99d80fd66224b7402d4fe62c8ffa7b",
"created_at": 1711760067,
"kind": 1,
"tags": [],
"content": "I just found out that Bisq2 was released.\n\nYou know, the thing with Java applications is that building them from source using Nix is really difficult. During the development of the Nix package for Bisq, I wrote a script which I would run to generate a Nix expression describing the Java packages which needed to be downloaded. Then another Nix expression would create a temporary (Maven) repository containing the downloaded dependencies. THEN, it was possible to build Bisq with Nix.\n\nBut I ran into a problem: I needed to include some DAO data and there was no way to get that in a reproduceable way, causing the build to fail when the DAO data was updated by upstream. I did find a solution. It so happened that the upsteam Linux package included the DAO data. I realized that I could get the DAO data from that file, solving the reproduceability problem. But at that point I also realized that if I was going to have to download the upstream linux package to get the data I needed, why not just repackage upstream's package for NixOS? This is the reason why the current Nix Bisq package is a repackaging up upstream's package, rather than a source build.\n\nI don't know why I'm saying all of this, other than perhaps I'm feeling uncharacteristically chatty today.\n\nI'm going to take a look at Bisq2 and create a Nix package for it. I can guarantee that I won't be building it from source ;)",
"sig": "34487ba86bed01c71e8a57ed2f07dfe8f1a23826c41b52cc59086461e2cf28341cda268554986eb69187337497b8cead634a705dcb95012a6cefa3e9eb8507a6"
}