search

hugopl / tijolo

Simple and fast keyboard focused IDE written in Crystal and GTK.
MIT License
144 stars 8 forks source link

Add "Available in nixpkgs" in README #11

Open sund3RRR opened 1 year ago

sund3RRR commented 1 year ago

https://search.nixos.org/packages?channel=unstable&show=tijolo&from=0&size=50&sort=relevance&type=packages&query=tijolo

hugopl commented 6 months ago

Nix package is outdated now.

sund3RRR commented 6 months ago

Nix package is outdated now.

Hi, Hugo! I don't want to update crystal packages, that depends on gi-crystal now, because I'm waiting for approval of my PR to main function, that builds crystal packages in nixpkgs repo. Shortly, it's a bad idea to package gi-crystal, because each package require spicific version of gi-crystal and updating this thing cause packages to break. So I'm waiting this changes to be approved to add ability for packaging crystal packages without pain in ass.

hugopl commented 6 months ago

I never understood why NixOS needs a package for every source dependency of a crystal program, basically re-doing what shards already does, is this because there are some policy that no download must be done while generating a package? Just declaring it needs version X of the GTK dependencies wouldn't be enough? I mean... if each crystal shard needs its own Nix package this sounds like a lot of work. Anyway... sorry for my ignorance regarding Nix packages and NixOS.

BTW I want to move code generation from compile-time to release-time. Nowadays if for example Harfbuzz releases a new source and binary compatible version that breaks gi-crystal code generation all releases wont compile anymore unless you have a version of harfbuzz that doesn't break gi-crystal installed. Moving the code generation to release-time would fix this and guarantee that source distributions would work in the future.

sund3RRR commented 4 months ago

Hi, Hugo! I think it's my fault. I decided to package gi-crystal, but then I realized that the version of gi-crystal for each package must match the version from shard.yml. So, updating packages that depend on gi-crystal becomes a pain in the ass. But at the time of packaging "Collision" I did not find a better solution. But now, after a couple of days of researching nix sources and answering the question why I can't use gi-crystal in nix derivations, I have discovered the main problem. I made a patch for the buildCrystalPackage function and fixed the problem. So gi-crystal can be removed from nixpkgs as now I can use it without packaging and patches.

I did a PR updating tijolo to 0.8.1. Very nice fresh GUI, your app looks beautiful! Thank you for your work.

hugopl commented 4 months ago

I did a PR updating tijolo to 0.8.1. Very nice fresh GUI, your app looks beautiful! Thank you for your work.

It just need tons of basic features yet for being usable by general public 😅. I need to take care of two babies now, so the tons of basic features will need to wait a bit.

sund3RRR commented 4 months ago

I did a PR updating tijolo to 0.8.1. Very nice fresh GUI, your app looks beautiful! Thank you for your work.

It just need tons of basic features yet for being usable by general public 😅. I need to take care of two babies now, so the tons of basic features will need to wait a bit.

Yeah, I wanted to open the preferences, but I couldn’t :)) I thought I packaged Tijolo incorrectly, but then I looked at the readme and realized that the preferences window just hasn't been implemented yet :)