[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] rfc: Go ebuilds bundling multiple upstream sources
From:       Zac Medico <zmedico () gentoo ! org>
Date:       2015-06-29 22:46:19
Message-ID: 5591CABB.6040706 () gentoo ! org
[Download RAW message or body]

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

[prev in list] [next in list] [prev in thread] [next in thread]