[erlang-questions] A plead to use tags (or equivalent in your SCM system)

[Tim Watson]

Thanks autocorrect - I'm not entirely sure that maintaining a 'dork'
involves, but it sounds even worse than maintaining a 'fork' anyway!

On 25 April 2012 09:18, Gmail <watson.timothy@REDACTED> wrote:
> Massive +1 on this point. It's really hard to rely on stuff that isn't tagged and either the author has to maintain a dork of these libraries they depend on so as to control the changes (which is really quite a headache) or simply 'hope for the best). Neither of which is a good solution. Please version and tags your components if you intend them to be re-used!
>
> Sent from my iPhone
>
> On 24 Apr 2012, at 20:43, "Heinz N. Gies" <heinz@REDACTED> wrote:
>
>> Hi I've noticed that a lot of libraires depend on bleeding edge data I kind of find that disturbing it makes maintaining a stable environment close to impossible since one never knows
>>
>>
>> what I mean are lines like this:
>>
>> {alog, ".*", {git, "https://github.com/siberian-fast-food/alogger.git", {branch, "master"}}}
>>
>> now if the alogger people push a breaking change your application breaks when depending on it, even worst if you don't even use alogger yourself but a library you use uses it a change in alogger would break your application without you having direct influence on it :(.
>>
>> So what I'd love to ask people who maintain libraries is use dependencies that have a fixed version and tag your own versions so people can do the same when using your stuff - please?
>>
>> Regards,
>> Heinz
>>
>> PS: I just choose alogger as an example since it was the first I found - I love the thing :)
>>
>> --
>> Heinz N. Gies
>> heinz@REDACTED
>> http://licenser.net
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions