Page 2 of 2

Re: Splitting Virtualbox.xml configuration into settings and stateful data

Posted: 10. Aug 2017, 09:53
by cluelesscoder
As I said above, I'm OK with raising awareness. But keep in mind that most of the Unix tools out there - ranging from little CLI tools configured with environment variables, e.g. ls to full-fledged desktop environments - split configuration and data as well, and they are not enterprise software. Users typically don't share their configs for these tools except as open-source "dotfiles" repos (see, e.g. https://dotfiles.github.io/).

Re: Splitting Virtualbox.xml configuration into settings and stateful data

Posted: 10. Aug 2017, 13:38
by Perryg
I really don't understand all the fuss. I have certain things that I dislike about VirtualBox but instead of pondering how to entice the DEVs to do what I think is correct I change them myself and build my own version that does what I want. Sounds like you have the ability to do the same, so why not just do it and be done with it.

Since the DEVs have to make all of this cross platform compatible they have to really be careful what and where they change things, and are usually not inclined to fix something that is not broken in their opinion, so there's that.