Skip to content

chore: Add .flox/ as generated by flox init for https://flox.dev (Nix) [skip changelog]#10763

Closed
vorburger wants to merge 1 commit intoipfs:masterfrom
vorburger:flox
Closed

chore: Add .flox/ as generated by flox init for https://flox.dev (Nix) [skip changelog]#10763
vorburger wants to merge 1 commit intoipfs:masterfrom
vorburger:flox

Conversation

@vorburger
Copy link
Copy Markdown
Contributor

As a #DevEnv, to make it easy to Build from Source. e.g. on (current!) Fedora 41 which still has Go 1.23 instead of 1.24.

See https://flox.dev

Ran into this while trying to locally further debug #10762 myself, but couldn't even get it to build, at first.

Please update docs/changelogs/ if you're modifying Go files. If your change does not require a changelog entry, please do one of the following: - add `` to the PR title

Done!

  • label the PR with skip/changelog

I don't appear to have the permission to do that on this repo - can I get it?

…ix) #DevEnv to make it easy to Build from Source e.g. on (current!) Fedora 41 which still has Go 1.23 instead of 1.24
@vorburger vorburger requested a review from a team as a code owner March 22, 2025 16:26
@lidel
Copy link
Copy Markdown
Member

lidel commented Mar 23, 2025

@vorburger thank you for submitting this. Unfortunately we can't accept this PR.

Rationale:

  • Our policy is to not include any editor / IDE specific code / package manager-speciifc code, as maintenance cost is taking limited time maintainers have away from working on bugfixes and features.
  • Files you introduce in this PR are specific to SaaS(?) startup/business at https://flox.dev and require maintenance. Nobody on the team is using https://flox.dev – without additional CI workflow that confirms these things work, it will get out of date as soon new golang is released. This is adding unnecessary noise/work.
  • If you want to create packages for local dev with specific editor/IDE or Linux distribution, follow what others did, and do that in your own repository:

@lidel lidel closed this Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants