The developers of Game Dev Tycoon have finally detailed the actual reason on why the Linux version isn't yet on Steam and isn't as up to date as the Windows and Mac versions.
You may remember we spoke to them about why Linux has fallen behind and they couldn't actually tell us why, now we know then!
The basics of it are that they use glibc that is under the Lesser General Public License (L-GPL) that can be used in commercial applications, but they didn't note that down anywhere and didn't include the license file along with it. It seems like an easy mistake as they say they use the node-webkit package which itself uses glibc on Linux, but the node-webkit package apparently doesn't note down it uses it (so it's not directly their fault they claim).
Sad when things like this happen it's not just the developer suffers, but so do we. Thankfully it seems like it can be easily resolved with their blog post by noting it's used on their website and including the license with the games files.
Although their blog post says they will offer the license on their credits page, if you read the credits page the license text states it should be included with the software, I hope they don't miss that out and have problems again so I have made sure to point this out to them.
I hope the FSF re-instates their rights to use it soon so we can get an updated version and have it on Steam.
Trailer
I will most likely pick myself up a copy once this is all resolved as I love this type of sim game.
How do you feel about this folks? Could things like this catch out more developers? Is there something we can do to help them?
Article taken from GamingOnLinux.com.
You may remember we spoke to them about why Linux has fallen behind and they couldn't actually tell us why, now we know then!
The basics of it are that they use glibc that is under the Lesser General Public License (L-GPL) that can be used in commercial applications, but they didn't note that down anywhere and didn't include the license file along with it. It seems like an easy mistake as they say they use the node-webkit package which itself uses glibc on Linux, but the node-webkit package apparently doesn't note down it uses it (so it's not directly their fault they claim).
Sad when things like this happen it's not just the developer suffers, but so do we. Thankfully it seems like it can be easily resolved with their blog post by noting it's used on their website and including the license with the games files.
Although their blog post says they will offer the license on their credits page, if you read the credits page the license text states it should be included with the software, I hope they don't miss that out and have problems again so I have made sure to point this out to them.
I hope the FSF re-instates their rights to use it soon so we can get an updated version and have it on Steam.
Trailer
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Direct Link
Direct Link
I will most likely pick myself up a copy once this is all resolved as I love this type of sim game.
How do you feel about this folks? Could things like this catch out more developers? Is there something we can do to help them?
Article taken from GamingOnLinux.com.
0 Likes
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
It is the price for doing things in a professional manner. While trying to be supportive to developers is often the right thing to do, they are trying to make money off a game title, and if they are hoping to seek financial gain from a free software project they have to do things properly otherwise they are abusing other people's work for their own gain. So I really do not see why I should be terribly sympathetic in this case. It is a not a huge faux pas on their part, and I am not angry at them for their mistake, but I am not terribly sympathetic to them simply because they were affected by their error.
0 Likes
I don't get it. So they violated the license by not including the license text. FSF cannot revoke or reinstate the LGPL. You either comply or you cannot use the software. Simple as that. Unless Steam somehow prevents you from including a license file/text in you product, I really cannot see the point here.
0 Likes
commodore256 Sep 7, 2013
You can still sell closes source software without paying FSF and comply with the license of of the (L)GPL.
0 Likes
Well, not like the FSF is known for being particularly rational or non-douchy when it comes to these things. Those people would much rather just see all "non-free" software dead and gone.
0 Likes
Am I just getting paranoid or have they completely removed all mention of the linux version from the front page of their website?
0 Likes
Quoting: DudeskiWell, not like the FSF is known for being particularly rational or non-douchy when it comes to these things. Those people would much rather just see all "non-free" software dead and gone.
How is the FSF defending the rights of those who use their license make them acting like a douche? The Game Dev Tycoon developers made a mistake and violated the license; actions have consequences.
0 Likes
I sure hope it is resolved, and hope it doesn't happen to any other dev.
0 Likes
Quoting: HamishI disagree. The license violation was so minimal it's unreal. The GOL article actually makes the facts less clear, which you can see for yourself at this post on the game's forum by our very own Liam Dawe.Quoting: Quote from DudeskiWell, not like the FSF is known for being particularly rational or non-douchy when it comes to these things. Those people would much rather just see all "non-free" software dead and gone.
How is the FSF defending the rights of those who use their license make them acting like a douche? The Game Dev Tycoon developers made a mistake and violated the license; actions have consequences.
They left a mention. All they did was just not include the license! Absolutely ridiculous. Personally I disagree with the FSF and while I prefer open source software in most cases, I believe it can and should coexist with proprietary software. I didn't realise that the fact the entire codebase is copyrighted to the FSF could have such an impact.
I'm surprised in general to have seen the FSF getting its panties in a bunch over this when I've seen much more serious breaches of this type from proprietary and open source software alike.
0 Likes
Quoting: SuperuserI'm surprised in general to have seen the FSF getting its panties in a bunch over this when I've seen much more serious breaches of this type from proprietary and open source software alike.
Yes, but because it was an FSF project they were actually able to become aware of it. Most breaches happen because they go unreported.
And ideology has nothing to do with this case, it is purely a legal matter.
0 Likes
Quoting: SuperuserHow does my article make the facts less clear, I very clearly laid out exactly what happened. Also my post on their forum to them was to point out a flaw in what they said they will do to clear it up (when the license text states it should be with the software, they should do that not tell people to go to the credits page).Quoting: Quote from HamishI disagree. The license violation was so minimal it's unreal. The GOL article actually makes the facts less clear, which you can see for yourself at this post on the game's forum by our very own Liam Dawe.Quoting: Quote from Quote from DudeskiWell, not like the FSF is known for being particularly rational or non-douchy when it comes to these things. Those people would much rather just see all "non-free" software dead and gone.
How is the FSF defending the rights of those who use their license make them acting like a douche? The Game Dev Tycoon developers made a mistake and violated the license; actions have consequences.
Yo quote myself:
Quoting: liamdaweThe basics of it are that they use glibc that is under the Lesser General Public License (L-GPL) that can be used in commercial applications, but they didn't note that down anywhere and didn't include the license file along with it. It seems like an easy mistake as they say they use the node-webkit package which itself uses glibc on Linux, but the node-webkit package apparently doesn't note down it uses it (so it's not directly their fault they claim).That is exactly what happened.
0 Likes
Patreon
PayPal
See more from me