sorry, mistake,

** My point is not criticize, but the way you describe the *how*
that pipeline should happen IRL.
That desciption seems taken from
controlled environment such as 
- internal company
- oss distro

On Friday, May 5, 2017 at 2:57:44 PM UTC+2, mhh...@gmail.com wrote:
>
> yeah i agree.
>
> But (:/), i think its pipeline issue in the consumption of a go package.
>
> In the same way the language is made to prevent user errors (as much as 
> possible, and its difficult)
> that go get pipeline usage should help in that matter too.
>
> My point is not criticize, but the way you describe the *how*
> that pipeline should happen IRL seems taken from
> controlled environment such as 
> - internal company
> - oss distro
>
> where every users is somehow subordinated to a common decision taker, a 
> commander ;)
>
> Typically inside google you can use such rules and later blame the end dev 
> which did not followed it.
>
> On the internet it is much less possible.
>
> And yes hopefully, so far, only one ticket :)
>
> But scale it by number of package providers * number of package users and 
> you get a mess of repeated questions, 
> no ?
>
>
> On Friday, May 5, 2017 at 2:47:51 PM UTC+2, Jakob Borg wrote:
>>
>> On 5 May 2017, at 14:41, mhh...@gmail.com wrote: 
>> > 
>> > Just to add on this that the fact i provide pre built bin is not 
>> winning against go get, 
>> > 
>> > The repo i took as example is providing, 
>> > https://github.com/mh-cbon/emd/releases 
>> > 
>> > and all possible ways to install it i can provide, 
>> > https://github.com/mh-cbon/emd#install 
>> > 
>> > So yeah i did my best, i loosed. 
>>
>> You don't have *that* many issues opened. :) Here you are probably 
>> targeting developers. They may be somewhat more likely to grab it from 
>> source than others. They can probably also answer the question "what git 
>> hash did you build from?" if that seems relevant. 
>>
>> On issues from other users I can usually get a feeling for whether the 
>> bug is something I expect or something that should not be possible. If the 
>> latter and the build seems suspect, "can you retry this with the latest 
>> official build please?". 
>>
>> But yeah. The source is out there, you can't *prevent* people from 
>> compiling it. (Other than not being go-gettable, which has advantages and 
>> disadvantages.) 
>>
>> //jb
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to