havok, on 05 April 2013 - 01:15 PM, said:
The post was trolling but had truth behind it which I wanted to uncover.
The first post already covered the main problem very bluntly. So there was nothing to uncover. I don't want to start a politeness contest here, but I was not rude either.
havok, on 05 April 2013 - 01:15 PM, said:
For the updater - it is in development so I am unable to comment on it's future features at this time
Well, you did and it was vague and confusing.
havok, on 05 April 2013 - 01:15 PM, said:
This is something that I would love to get resolved. There is a reason that Steam does things that way, which is the system behind the platform, steam works off user authentication which is essential in today's gaming environment as it means they can sync settings, account details, etc, etc. Something that could be quite interesting though is a hybrid solution that utilises the package managers AND the updater.
No, that is not possible. At least not without completely breaking the purpose of package managers and how they handle, verify, install and set permissions on files.
havok, on 05 April 2013 - 01:15 PM, said:
I do not see what this has to do with trust, trust is only relevant if we 100% trust everyone who plays urban terror. Based on the number of people that hack in 4.1 how could we even think to trust them with the source code to the updater? That is the reason that it is closed source will remain that way.
Does not compute. When someone hacks opensource, then it's time to improve the source. Guess why the most important parts of server software (or rather all) is always opensource. And besides... closed source does not mean people will not hack it. Windows, any1? Nvidia driver hacks... and whatnot.
And even if I am wrong here (which is very well possible since I am not a game developer), we are still talking about an updater, not something like punkbuster.
havok, on 05 April 2013 - 01:15 PM, said:
No, the slowdown of the updater was not due to what is inside it. You also have to remember that although there is a large active linux community within urban terror, they are still a minority. The updater is very useful for windows and mac users. This is something that you need to take into account with every response, the fact that when the updater is working efficiently then it will work for everyone on every platform.
Given the case that people want to use it. It has a lot of disadvantages too, including precompiled binaries.
havok, on 05 April 2013 - 01:15 PM, said:
What I personally would like to see, is the updater being the core of the game and different ways of distributing the data initially.
I am a windows user primarily, so I want to see everything moving away from the old fashioned 'download a zip, extract it to a folder, edit a load of config files, manually type in auth' only to find that you downloaded the old version of the game and need to repeat it all.
Hasufell - you obviously know a lot more than me about linux and how packages are managed. How about writing a post of exactly how to give you a file that can be used across all distributions of linux, what to include on it and how you think it can be integrated with the updater for us to add more features on top.
That is simple: write a cmake based build system that compiles ioq3-for-UrbanTerror-4 and _optionally_ fetches the data files during BUILD, otherwise the user has to set a folder/zip file location where the data is assumed to be. Desurium does that for example.
That will work for windows, mac and all linux distros.
You have to understand that the updater will _never_ be compatible with package managers.
Binary package managers assume specially packaged tarballs (i.e. deb, rpm, pkg) that just contain files in a directory structure and additional meta information. These tarballs are created by the distributor, there is no to little gain for them with your updater. It rather makes the procedure for them more annoying.
Source package managers (e.g. portage or pacman) need the original upstream files present and available BEFORE it starts doing anything (like compiling). Those files have to be static and must not be fetched during build-time, because that breaks many features and usecases (including Manifests, offline installation and secure fetching) and is banned.
In both cases the installed files are static and are not allowed to change except by root/the package manager.
You cannot satisfy linux distros with your updater. Just let the distributors handle it. We know how to do that. Provide tarballs on time, non-broken and reliable and people will be happy to check on UT when they hear about a version bump.