On 05/29/2016 04:25, Ulrich Mueller wrote:
>> On Sun, 29 May 2016, Rich Freeman wrote:
>
>> What I would love to see is this be standardized. An eclass or a
>> GLEP seems like the logical approach.
>
> I am strongly opposed against this. Ebuilds should not source
> executable code from
On Sun, May 29, 2016 at 4:25 AM, Ulrich Mueller wrote:
>> On Sun, 29 May 2016, Rich Freeman wrote:
>
>> What I would love to see is this be standardized. An eclass or a
>> GLEP seems like the logical approach.
>
> If there really is a need for such a feature, we should rather
> On Sun, 29 May 2016, Rich Freeman wrote:
> What I would love to see is this be standardized. An eclass or a
> GLEP seems like the logical approach.
I am strongly opposed against this. Ebuilds should not source
executable code from random locations. This is also a huge QA
violation, since
On Sat, May 28, 2016 at 9:11 PM, Joshua Kinard wrote:
>
> Whether the idea is useful in the present day and age, eh, who knows. For the
> mips-sources ebuilds, eblits let me centralize the per-machine notes and
> unpacking logic, which reduced each ebuild's size from ~18KB a
On 05/26/2016 21:28, Kent Fredric wrote:
> On 27 May 2016 at 10:28, rindeal wrote:
>>
>> 1) what are they?
>> 2) why are they used?
>
>
> My best explanation is its a way to re-use very large amounts of code
> between 2 ebuilds, without resorting to:
>
> a) Copying the
On 05/26/2016 18:28, rindeal wrote:
> I've noticed that ebuilds for at least dev-lang/perl and
> sys-libs/glibc are using some concept of "eblits", which seems like
> parts of ebuilds scattered across $FILESDIR with ebuilds containing
> some logic (involving eval) which includes and runs them.
>
On Fri, May 27, 2016 at 9:28 AM, Kent Fredric wrote:
> That said, its a very confusing system to get your head around,
> because its *basically* yet another "mixin" system like "inherit", but
> done in bash, which itself is a rather strange language to be doing
> something
On Fri, 27 May 2016 00:28:35 +0200
rindeal wrote:
> 1) what are they?
A horrible QA violation.
> 2) why are they used?
Because some people like to feel special...
--
Ciaran McCreesh
On 27 May 2016 at 10:28, rindeal wrote:
>
> 1) what are they?
> 2) why are they used?
My best explanation is its a way to re-use very large amounts of code
between 2 ebuilds, without resorting to:
a) Copying the whole ebuild and hoping you find the relevant part in diffs