Am 01.12.2017 um 00:00 schrieb Ger:
> On 11/30/2017 03:21 PM, clipka wrote:
>> Am 30.11.2017 um 21:15 schrieb Ger:
>>> When trying to compile the latest povray-master on the latest opensuse
>>> tumbleweed I get the following
>>
>> As mentioned in the project's `README.md` file, we generally discourage
>> building from the master branch. Please build from any of the tagged
>> commits instead:
>>
>> https://github.com/POV-Ray/povray/tags
>>
>> The issue you've encountered should already be fixed in the latest and
>> greatest of those versions (currently v3.8.0-alpha.9387404).
>>
> I've used the povray-master file before and it always worked.
> tried 3.7.0.3 and it failed with the same error
> 3.7.0.4 works
> 
> I prefer to stay clear of anything that has "alpha" in the version and
> if I read you correct the master is the very latest uploaded and it's
> not guaranteed to work.

All our code is automatically test-built on various platforms (four of
them, to be precise), and if any of the test builds fails, we make it a
habit of fixing the code in a timely fashion. Moreover, we will never
tag such a broken version.

The problem you're suffering from was caused by a breaking change in the
boost libraries, which is beyond our control. We cannot avoid such
breakage, we can only clean up the damage after the fact. That hasn't
happened yet in the master branch.

The current master branch happens to /not/ be the latest uploaded code.
That would happen to be the `hotfix/issue_339` branch (which is a
3.7.0.4 derivative). However, the "latest and greatest" code is
currently maintained in the `release/v3.8.0` branch, which happens to be
at alpha stage.

BTW, the current master branch also has "alpha" in its version. It's
actually even more "alpha" than any tagged version, in that it doesn't
even have a dedicated pre-release ID number after the "alpha".


`release/v3.8.0` is where we maintain the version that's ultimately
going to become v3.8.0.

`master` is where we maintain any changes that are to be released in a
later version.

Since we're currently focusing on v3.8.0, that's where most changes are
happening; from time to time they will be merged into the master branch,
but at times the master branch may lag behind.

The old v3.7.0 is maintained in an entirely separate branch, and only
gets occasional updates to keep it "alive" (read: compile with modern
compilers and 3rd party libraries such as boost).


I hope this clarifies things a bit.

Post a reply to this message