Hi, > Niclas, Where did I say it was "Binary with link to Source?”
I would assume from your email here: > So, my assessment is: > 1) the binary artifacts are ok. No new problems. > 2) the source artifacts are not ok. There might be a workaround if we can > figure out how to convert the code page on those files. > 3) Would be nice to fix the executable bit on the scripts, but not a new > problem either. > So, the vast majority of our users may not hit this problem since they > consume the binary artifacts and not the source artifacts. I'll leave it > up to Piotr as to whether he wants to roll another RC that picks up > changes. i.e. That you were good to release the working binary and broken source artefacts together. I did also raise this as a issue , although perhaps in a less direct way. > Either way it's the source that’s the offical release and it seems unusual to > release a broken source release even if the binary did work. Given there’s going to be another RC perhaps it would be better to not waste energy arguing about this? Thanks, Justin
