Piotr Masłowski

> Also there's a somewhat unofficial feature where you can change a pkgbuild, commit it back and as long as there are no conflicts yay will happily merge it with...

I believe it should be agreed whether or not Yay is responsible for tracking the changes in the build instructions. Then it could be either closed or marked as intended...

@JuniorJPDJ Yeah, this would suggest that it is an intended feature. But right now it is partially broken, or at least does not play nice with the rest. I also...

.

I'll just add that it's not only a problem with nested `Maybe`s. It also breaks when using `Maybe Value`: ```haskell fromJSON . toJSON $ Just Null :: Result (Maybe Value)...

@rcaelers I'm not sure if you know about this, but the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) now differentiates between data and state (defaulting to `~/.local/share` and `~/.local/state` respectively). It's roughly equivalent...

> The above are just examples of possible metrics that might be used, but would need to be tested for correlation (re: confidence). > > How to do this then?...

I hit the same issue. Python: python-3.10.2-1 from Arch Linux `scikit-surprise` from `pip` within a venv: ``` (.venv) [piotr@andrad ...]$ python -c 'import surprise; print("surprise", surprise.__version__)' Traceback (most recent call...

Just for completeness sake: 0 packages -> pakietów > 1 package -> pakiet > 2-4 packages -> pakiety > 5+ packages -> pakietów

Hmm, I think I came up with an approach that would be both simple to implement and largely backwards-compatible with people's expectations: If `~/.var` exists, use it else, if `{XDG_STATE_HOME:-~/.local/state}/flatpak`...