Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24583 - [go] split go into a go and a go-docs package
Attached to Project:
Community Packages
Opened by Alexandre Bique (babali) - Sunday, 05 June 2011, 11:21 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 12 April 2012, 05:25 GMT
Opened by Alexandre Bique (babali) - Sunday, 05 June 2011, 11:21 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 12 April 2012, 05:25 GMT
|
DetailsDescription:
Create a third package to share files (doc, misc files) between gcc-go and go. Also move some files in the right place, for exemple /usr/share/go/misc/emacs could go in /usr/share/emacs/site-lisp |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Thursday, 12 April 2012, 05:25 GMT
Reason for closing: None
Additional comments about closing: Splitting into a doc package doesn't seem to be needed. The emacs files should be in the right place.
Thursday, 12 April 2012, 05:25 GMT
Reason for closing: None
Additional comments about closing: Splitting into a doc package doesn't seem to be needed. The emacs files should be in the right place.
But symlinking emacs files in /usr/share/emacs/site-lisp is a good idea.
Also i tried some "goinstall" and it failed every times, so i decided to build an updated revision of go, and then goinstall worked very well. So could you update go to a newer revision ?
Thanks a lot!
Random Go enthusiast here.
If goinstall fails, it could be that the packages are written for a newer version of Go (this happens often), but also make sure to check that goinstall has permissions to write.
Please flag "go" as out of date if it's out of date, or open a ticket if there are problems with the default file permissons (or with goinstall).
I've also heard rumors that setting environment variables so that goinstall write to a place in the home directory may work, but I haven't tried this method yet.
Best of luck.
- Alexander