On 06/29/2015 02:27 PM, William Hubbs wrote: > All, > > we have several Go ebuilds in the tree that bundle multiple separate > upstream sources. One example is app-admin/consul-0.5.2. > > My thought is that we shouldn't bundle like this, but we should figure > out how to write ebuilds for the dependent packages as well. > > What do others think?
Maybe we should take into account the number of consumers of said libraries? If there's only one consumer of a given library, then what's the advantage of splitting out a separate ebuild? Also, in our discussion, it may be useful to distinguish between bundling via "one big tarball" versus bundling via multiple tarballs in SRC_URI. -- Thanks, Zac
