Many Go tools have fairly generic names. Aren't you afraid of a (possibly
future)
naming conflicts by placing them all in /usr/bin/?
--
Pierre Neidhardt
On 2017-03-21 11:14, Bartłomiej Piotrowski wrote:
> On 2017-03-08 17:13, Iru Cai via arch-general wrote:
>> Hi,
>>
>> I'm not familiar with go, but I'm trying to use some go programs, caddy for
>> example. I read the PKGBUILD of it. It first use `go get' to get the
>> dependencies and then do the `
On 2017-03-08 17:13, Iru Cai via arch-general wrote:
> Hi,
>
> I'm not familiar with go, but I'm trying to use some go programs, caddy for
> example. I read the PKGBUILD of it. It first use `go get' to get the
> dependencies and then do the `go build'.
Yes, that's a bad practice, and the fact tha
On 20.03.2017 20.48, Eli Schwartz via arch-general wrote:
You seem to be taking it for granted, that people will somehow magically
agree with you that a unified multi-package is an optimal state of
affairs, and are looking to find out if there is any valid defense of
the status quo.
Ah, I was
4 matches
Mail list logo
