So you can basically replicate person’s system in your container and play with it?

but it’s much heavier

its not me

totally agree

the gnome/gimp toolkit has always been and will probably always be a mess

which is why i prefer to qt xd

damn 618 bug issues and they request -=cool=- ..::EFFECTS::.. instead of donating to full-time developers

well, for one, he asked politely
and two, if you can’t listen to your users, then why be a maintainer at all
(there are rude people, but just closing a PR without an explanation too is rude)

this tbh.

i’ve said it in this group before: there’s always drama around drew devault xd

i tried qtile wayland and it works, but i couldn’t set up the input configuration stuff

means no dwt and tap-to-click for touchpad
pain

damn

things i like about qtile, and i haven’t even tried it yet:
1) python, my favourite language
2) native wayland support wlroots 😎
3) native x support (without relying on xwayland)

wayfire’s cool
but there’s this bug: if i click the close button, the whole wm crashes

yay, I am first

x support in a wayland environment without xwayland? how

i never said “in” wayland

you can run it on xorg natively, and you can run it on wayland natively

i’m assuming it also supports xwayland, but i haven’t tried it

it does

I saw a shkxd tool for wayland ti use keyboard

He said qtile support xorg apps natively

I never got the hang of nix, as I’m really put off by their package format, but nixery seems pretty darn cool. You pull or run a docker image named with all the packages you want, and it’s magically built for you

using an image name like nixery.dev/shell/git/htop

or like

podman run -it –rm nixery.dev/zsh/git/busybox/python3/shadow/sudo zsh

did someone use homebrew or nix? what are the diferencces and adventages or drawbacks between them and a normal package manager?

Just moved to mac 2 weeks ago. I use brew

Really like it. Makes life easier. Try to install every single thing with it. Don’t do manual installs

So later on you can do brew list and put that in a file to later on use it. Like pip freeze

IMO, on a mac, it’s generally most practical to use brew for everything. But nix shines when you want to define reproducible environments that will work the same on any machine. This nixery thing looks super handy.

I will check it out didn’t even consider since brew is what most use seems like

And it’s well maintained

sound more interesting I might give it a try. But I wonder if a Artix Linux user (arch but without systemd) I would really need it at all….

what type or reproducible environment do you need?

I don’t use nix, as I currently define reproducible environments as containers, built with shell scripts and buildah.

But someone just opened my eyes to nixery, using it in a bug report to create a reproduction of the bug (that the main dev couldn’t reproduce locally), and nix+nixery seems great for that.

I might try using it for more general container definitions.

wow arch repos have nix!XDDD

hm. so you can basically replicate person’s system in your container and play with it?

seems cool 🤔