5 ms·
What exactly would it mean to exclude features from an edition you provide the source for? Wouldn't anyone just be able to get a copy of the source and build th
by ivanbakel 9y ago
What exactly would it mean to exclude features from an edition you provide the source for? Wouldn't anyone just be able to get a copy of the source and build the fully-featured edition anyways? How would these features even migrate - surely you could patch them back in to future version.
- the_common_man 9y agoRight, that's the point. People who want it all for free and don't want to pay citrix anything are free to do so by compiling it from the source. This is 'unsupported' by citrix and you are free to do whatever you want. The binaries as provided by citrix come in 3 editions. These changes apply to those editions. These are 'supported' by citrix.
- ivanbakel 9y agoInteresting to know - so you're paying for the support contract, but just indirectly? Makes me wonder if that gives Citrix an interest in opposing deterministic binaries.
- jrochkind1 9y agoWhat license is the source distributed under? I think any licenses that are truly open source would allow anyone else to distribute binaries too, so people could get binaries from such a distribution rather than compile themselves. I guess there might be a reason compiling to distribute binaries would be a time-consuming pain? (Or compiling yourself, for that matter).
- eggsome 9y agoOk, but the problem is nobody seems to have the interest in recompiling it for the community (think CentOS). A few months ago they started charging for patches and someone asked in the XenServer forums here: https://discussions.citrix.com/topic/390349-open-source-fork-of-xenserver/ https://discussions.citrix.com/topic/390349-open-source-fork...
- exikyut 9y agoWhen and how (frequently) do the security patches get folded into the source tree?