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