pce 20160308 (devel)

[tomyun]

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Formulae Submissions:

• Does your submission pass
  brew audit --strict --online <formula> (where <formula> is the name of the formula you're submitting)?
• Have you built your formula locally prior to submission with brew install <formula>?

[dunn]

This is probably going to be computed as a lower version than the previous, so we should probably leave it scanned from the URL.

[tomyun]

They seem to alternate version schemes between stable and unstable versions. For example, they had 20130218 between 0.2.1 and 0.2.2. I know prefixing version in this way may break some existing users for now, but the current devel version will prevent upgrading to stable versions later anyways. Another thing is that version scanning didn't work correctly with their filenames. The version was supposed to be 20140222, but was set to 20140222-4 due to the following hash part.

[dunn]

Even if upstream alternates their version scheme, we can always use the date. Would that work?

[tomyun]

Do you mean that we would use the date for even stable versions? I thought the other way around. We could always use numerics (0.x.x) and optionally add date for unstable release. The current formula already uses stable version 0.2.2.

[tomyun]

Or does brew distinguish versions between stable and devel? i.e. no upgrade from devel to stable even if higher stable versions available?

[dunn]

Or does brew distinguish versions between stable and devel? i.e. no upgrade from devel to stable even if higher stable versions available?

Yep!

[tomyun]

A new thing that I just learned! Okay, the formula is updated to conform the current scheme.

[dunn]

Merged as Homebrew/homebrew-core@4c859fc, thanks again!