| 1 |
On 06/30/2015 03:08 PM, William Hubbs wrote: |
| 2 |
> The source code is where the compatibility between versions of Go is, |
| 3 |
> not the static objects, so what if, for third-party go packages, we |
| 4 |
> skip installing the static objects? |
| 5 |
> |
| 6 |
> The only down side of this would be that there might be longer rebuilds |
| 7 |
> if the packages have multiple consumers, but it gets rid of the static |
| 8 |
> objects. |
| 9 |
> |
| 10 |
> What do you think? |
| 11 |
|
| 12 |
I'll give real example involving go-tools. The go-tools build requires |
| 13 |
go-net, which in turn requires go-text. If the go-net *.a files are |
| 14 |
installed, then it is possible to build go-tools against go-net without |
| 15 |
having go-text installed. If the go-net *.a files are not installed, |
| 16 |
then you will have to install go-text before you can build go-tools. It |
| 17 |
introduces an indirect build-time dependency between go-tools and go-text. |
| 18 |
-- |
| 19 |
Thanks, |
| 20 |
Zac |
Archives