> You're missing the point, confirming the generally dismissive or even ignorant attitude.
I get the issue if you're still dealing with chroots. I hated this with a passion, too - but using Docker is a real breeze in comparison.
> What if there's no deb package?
A Debian archive docker image behaves just like an ordinary Debian install would - they are fancy chroots. Install the dependencies, run the usual "./configure && make && make install" dance, that's it.
> How to make home directory accessible?
Add a "-v /home:/home" in the invocation.
> The point was, every time Gtk/Qt major version is updated, whole desktop gets obsolete. Perfectly fine applications must be reworked or abandoned or mucking with chroot/docker. Throw in the transition to systemd and wayland.
Agree with you on that one, with one exception... systemd unit files are so much easier to deal with than init.d shellscripts.
I don't trust systemd and docker, sorry. No idea if it's my bad luck or what, every time I tried out such a complex thing with "easy" interface, I ran into some insidious bug.
I get the issue if you're still dealing with chroots. I hated this with a passion, too - but using Docker is a real breeze in comparison.
> What if there's no deb package?
A Debian archive docker image behaves just like an ordinary Debian install would - they are fancy chroots. Install the dependencies, run the usual "./configure && make && make install" dance, that's it.
> How to make home directory accessible?
Add a "-v /home:/home" in the invocation.
> The point was, every time Gtk/Qt major version is updated, whole desktop gets obsolete. Perfectly fine applications must be reworked or abandoned or mucking with chroot/docker. Throw in the transition to systemd and wayland.
Agree with you on that one, with one exception... systemd unit files are so much easier to deal with than init.d shellscripts.