On 06/29/2015 07:24 PM, Michael Orlitzky wrote:
> On 06/29/2015 07:44 PM, Zac Medico wrote:
>>
>> While it would certainly be possible to split out a number of separate
>> ebuilds for Go libraries that are used *exclusively* by consul, what
>> advantages would it have?
>
> Even in this limiting ca
On 06/29/2015 07:08 PM, wirel...@tampabay.rr.com wrote:
> On 06/29/2015 06:50 PM, Zac Medico wrote:
>> On 06/29/2015 05:27 PM, wirel...@tampabay.rr.com wrote:
>>> On 06/29/2015 05:50 PM, Zac Medico wrote:
On 06/29/2015 02:27 PM, William Hubbs wrote:
> All,
>
> we have several Go eb
On 06/29/2015 07:44 PM, Zac Medico wrote:
>
> While it would certainly be possible to split out a number of separate
> ebuilds for Go libraries that are used *exclusively* by consul, what
> advantages would it have?
Even in this limiting case,
1. You avoid pointless rebuilds. You rebuild the l
On 06/29/2015 06:50 PM, Zac Medico wrote:
On 06/29/2015 05:27 PM, wirel...@tampabay.rr.com wrote:
On 06/29/2015 05:50 PM, Zac Medico wrote:
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 a
On 06/29/2015 05:27 PM, wirel...@tampabay.rr.com wrote:
> On 06/29/2015 05:50 PM, Zac Medico wrote:
>> 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.
>>>
On 06/29/2015 05:50 PM, Zac Medico wrote:
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 h
On Saturday 27 of June 2015 21:39:35 Johannes Huber wrote:
Feel free to keep me there.
(although my usefulness has lessened of late...)
regards
MM
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 dep
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?
William
