Opened 21 months ago
Closed 21 months ago
#65597 closed defect (wontfix)
go: reduce install footprint
Reported by: | mascguy (Christopher Nielsen) | Owned by: | herbygillot (Herby Gillot) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.2 |
Keywords: | Cc: | ci42 | |
Port: | go |
Description
Presently this port installs more than 10,000 files. 7,000+ are source-related, while 2,500+ cover tests:
$ port contents go | wc -l 10650 $ port contents go | ggrep "/opt/local/lib/go/src" | wc -l 7232 $ port contents go | ggrep "/opt/local/lib/go/test" | wc -l 2553
In addition, on Intel, amd64-related binaries - which presumably aren't helpful? - are also installed:
$ port contents go | ggrep "/opt/local/lib/go/pkg/darwin_amd64" | wc -l 427
Is all of this necessary, for a standard install?
Change History (3)
comment:1 Changed 21 months ago by mascguy (Christopher Nielsen)
comment:2 Changed 21 months ago by herbygillot (Herby Gillot)
Go is a "batteries-included" programming platform, and everything you've listed is needed.
If you download the *official* installer package from https://go.dev, you will see that it contains the same, installing everything, including source, tests, and the contents of 'pkg'.
Attempting to mess with the package contents, or trying to partition certain pieces off into separate ports will result in a very bad experience for Go users using MacPorts as compared to other packaging environments, and may even cause Go to fail and malfunction for a sizable number of standard use cases.
Users expect to just install go
and see that everything is available and just works.
comment:3 Changed 21 months ago by herbygillot (Herby Gillot)
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
If the sources and tests aren't necessary for dependents, perhaps they could be encapsulated in separate compressed tarballs?