Comments (9)
Well hopefully #124, should save a bit of hassle when it comes to tracking, otherwise it might be cool to have a changelog.
from nix.
You might consider @infinisil's approach he's been working on. NixOS/nixpkgs-check-by-name#38
from nix.
Well hopefully #124, should save a bit of hassle when it comes to tracking, otherwise it might be cool to have a changelog.
This repository uses release-please but I don't believe a release has been cut yet for the changelog to exist. I'm not sure what @getchoo's plan is for v1 before merging #65 but I'd personally have probably merged v1 when it got transferred into the organisation
from nix.
I'm not sure what @getchoo's plan is for v1 before merging #65
in all honesty, i'm not sure either. this is an issue i've definitely put to the side over the last few months, as i feel most releases would be fairly arbitrary (with the exception of v1 when the transfer happened...that would've made a lot of sense lol) with the current pace of additions. i also think some aspects of semantic versioning like bumping the major version for public api changes could introduce problems at the scale of so many ports. a good example would be changes in individual ports possibly changing appearance; would that be a breaking change? what about any ports that may be dropped by the org for some reason? would each of those constitute api breakage and a major release?
a solution i've been considering both for solving the problems with versioning and (more on topic with this issue 😆) is possibly having snapshot/date based releases. i think this would be more representative of the project's rapid additions with few (if any) backwards incompatible changes, and give a way to consistently update people on these changes at regular intervals
curious to here what others think would be a good approach here, since i know versioning in nix can be a pretty controversial topic
from nix.
curious to here what others think would be a good approach here, since i know versioning in nix can be a pretty controversial topic
Two things from me:
-
Ultimately, I don't mind what versioning scheme we use as long as we're consistent and stick to the rules that we end up defining. Regarding the existing semver versioning, I think it's a very slippery slope if you start to consider the actual changes to themes as breaking changes/features. I think the semver aspect should be purely contained to the actual repository (e.g. changing an existing option or removing an existing port would be a breaking change, adding new ports would be features, etc?)
Datetime based releases seem like a good option if we decide that semver doesn't make enough sense here, but it's worth noting that we'd have to rip out the existing release-please config.
-
I'm not too involved in the nix ecosystem but my first thoughts are to look at prior art and see what versioning schemes other repositories similar to ours use?
from nix.
Worth consideration:
https://lobste.rs/s/ynhu2s/effver_version_your_code_by_effort
https://jacobtomlinson.dev/effver/
from nix.
- Ultimately, I don't mind what versioning scheme we use as long as we're consistent and stick to the rules that we end up defining. Regarding the existing semver versioning, I think it's a very slippery slope if you start to consider the actual changes to themes as breaking changes/features. I think the semver aspect should be purely contained to the actual repository (e.g. changing an existing option or removing an existing port would be a breaking change, adding new ports would be features, etc?)
Datetime based releases seem like a good option if we decide that semver doesn't make enough sense here, but it's worth noting that we'd have to rip out the existing release-please config.- I'm not too involved in the nix ecosystem but my first thoughts are to look at prior art and see what versioning schemes other repositories similar to ours use?
I don't particularly think this repo needs releases at all. Since people can pin this flake to a certain commit. But If we really did want releases we could use flakehub.
And in terms of things breaking on this repo, nix provides some nice lib functions for renaming modules and removed ones and so on.
from nix.
#124 is good enough for me. Feel free to close the issue.
from nix.
A simple way to be notified of updates would be to follow the Atom feed for commtis to this repository, https://github.com/catppuccin/nix/commits/main.atom, though that of course wouldn't filter new additions from other types of commits.
from nix.
Related Issues (20)
- Hyprcursor theme is set to "MyCursor" HOT 12
- Overriding catppuccin flavor for individual hm modules HOT 3
- Maintain our own derivations of ports where necessary
- Is it possible to change the underlying theme colors? HOT 4
- Broken link in readme
- transparent_background and other options for catppuccin/nvim HOT 1
- Catppuccin options don't exist HOT 2
- Importing Home Manager creates a conflicts with Hyprland (even disabled) HOT 4
- GTK theme is not applied using home-manager HOT 1
- yambar support HOT 2
- bug: `ctp.kvantum` does not allow `qt.platformTheme.name = qtct` HOT 5
- Global enable doesn't work for GTK HOT 3
- Ports for other home-manager modules HOT 1
- Can't build on nixos unstable when enabled globally HOT 5
- How to increase size of rofi window?
- Expose color palettes as attr sets in top level module HOT 3
- [Qt] Setting QT_STYLE_OVERRIDE breaks QML apps
- IFD at all HOT 1
- mpv: add uosc
- Inconsistent scale in applications
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nix.