https://bugzilla.redhat.com/show_bug.cgi?id=1426790
Jakub Čajka <jcajka(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |jchaloup(a)redhat.com
Assignee|vbatts(a)redhat.com |jcajka(a)redhat.com
--- Comment #3 from Jakub Čajka <jcajka(a)redhat.com> ---
(In reply to Till Maas from comment #2)
Building seems to work with:
export GOPATH=$HOME/work:/usr/share/gocode
go build till/test/pty
This is intended way of use, if you want to use distribution libraries. I'm
actually writing blog post about basic workspace setup(although definitively
non-exhaustive). I will update the doc on devel portal to include these bits.
but AFAICS setting the GOPATH to include /usr/share/gocode also lacks
documentation and it still break go install.
This directories are distribution provided and are write protected from regular
users(IMO correctly), that leads to failure of go install(or go build -i).
There is question whatever we want to ship intermediate build artifacts for
non-standard libraries which IMHO we shouldn't want until we will switch
to/encourage dynamic linking, system wide(if at all). Maybe possibly just for
libraries that do releases and guarantee stable API(and leave it on
maintainer)? I think that is definitively still open question.
CC'ed jchaloupka
Thx to thm for finding this and the typo from comment 1
--
You are receiving this mail because:
You are on the CC list for the bug.