2 Apr
2017
2 Apr
'17
7:55 p.m.
Am 02.04.2017 um 19:42 schrieb Bernardo Barros:
On 4/2/17 1:34 PM, Ralf Mardorf wrote:
I would never "release" with a dependency to unreleased software. You
still cant consider it a release.
Software in git could change and render your release unusable without
give users a chance to know what going on.
As already suggested, if you in the need and hurry, include the
git-version you depend on within your release tarball is the way to go.
just my 2 cent
hermann
Christopher only mentioned, that it's not
wise to have a hard dependency
on something that isn't official released.
What if that's the only way?
"Program in a way that it doesn't the git
version"(?) It don't think it's a wise suggestion either without looking
for the reasons they did it.