kdeldycke
Joined 16 years ago
Karma
700
Submissions
146
Member since
Nov 5
Recent submissions
Comment · 4 months ago
Comment · 5 months ago
I have you covered: https://kdeldycke.github.io/meta-package-manager/install.htm...
(this is mpm, a Meta Package Manager)
Comment · 6 months ago
I maintain `repomatic`, a Python CLI + reusable workflows. It bakes most of the practices from this post into a drop-in setup for Python projects (uv-based, but works for others too). The goal is to make the secure default the easy default for maintainers who just want to ship packages. Also addresses a lot of GitHub Actions own shortcomings.
But thanks to the article I added a new check for the fork PR workflow approval policy.
Comment · 7 months ago
For the moment I consider that only one agent can be active. If multiple are detected, I raise an error. That is intentional to gather more context and feedback from users. I will change this behavior as soon as someone report me a use-case.
See the implementation at: https://github.com/kdeldycke/extra-platforms/blob/ecbe740bf7...
Comment · 1 year ago
Comment · 1 year ago
I have a project called Meta Package Manager that supports pURLs, so you can:
$ mpm install pkg:npm/[email protected]
Other commands allows you to export the SBOM of all packages installed on your machine. More info at: https://github.com/kdeldycke/meta-package-manager
Comment · 1 year ago
> My holy grail will still be landing on a good multi-layer configuration setup for Rust CLIs. Ideally CLI flags merged over top of environment variables merged over top of configuration files.
I did that for Python if you are interested: https://github.com/kdeldycke/click-extra
You create your CLI with Click as usual, then Click Extra introspects your "--parameters" to build up support for a corresponding configuration file in either TOML, YAML, JSON, INI or XML.
Comment · 1 year ago
> When I decided to write a post on ledgers, I already knew there were a few good resources out there to help me.
One that's not referenced in this article and compile all of them is: https://github.com/kdeldycke/awesome-billing#readme
Comment · 2 years ago
Yes you're right. It is not complete and had plan to fix all that a couple of years ago but put it on the back-burner. I'm still happy to merge PRs upstream from motivated contributors! :)
Comment · 2 years ago
They can scrap my CSV at: https://github.com/kdeldycke/vat-rates
Comment · 2 years ago
I ‘m using https://stork-search.net for my static website search, but it’s no longer maintained. So yeah, Tantivy would be a great candidate to replace it! :)
Comment · 2 years ago
Billing. It always has to be the billing. For a list of all other edge cases, you have: https://github.com/kdeldycke/awesome-falsehood#readme
Comment · 2 years ago
I compiled a list of these articles at: https://github.com/kdeldycke/awesome-engineering-team-manage...
For each one I tried to extract the key point or Tl;Dr in the description.
Comment · 3 years ago
We were discussing about Resolver One 6 months ago at: https://news.ycombinator.com/item?id=34819682
One mystery we did not resolve (pun intended) was why it did not find its audience. Was it too early? Was data science not established enough as a field? Was it because it was not Excel (i.e. the dominant tool)?
Nothing protect you from a `yay -S foo` install and its dependencies. So this is not a guarantee or enforcement of a minimum release-age.
Actually writing this reply I went ahead and pointed that out in an issue at: https://github.com/Jguer/yay/issues/2883