On Tuesday 14 August 2012 16:39:57 Michał Górny wrote:
> On Tue, 14 Aug 2012 12:46:30 -0700 Zac Medico wrote:
> > On 08/14/2012 02:44 AM, Michał Górny wrote:
> > > As some of you may have noticed, lately introduced 'double include
> > > preventions' have caused changes in effective phase functions
On Tuesday 14 August 2012 17:59:40 Zac Medico wrote:
> That just means that somebody made a mistake. They should have put the
> EXPORT_FUNCTIONS call *outside* of the ifndef block. Just educate people
> about the correct place to put the EXPORT_FUNCTIONS call, and that
> problem is solved.
sounds
On 08/14/2012 02:51 PM, Michał Górny wrote:
> On Tue, 14 Aug 2012 14:09:17 -0700
> Zac Medico wrote:
>
>> On 08/14/2012 01:54 PM, Michał Górny wrote:
>>> On Tue, 14 Aug 2012 21:45:56 +0100
>>> Ciaran McCreesh wrote:
>>>
On Tue, 14 Aug 2012 11:44:49 +0200
Michał Górny wrote:
> As s
On Tue, 14 Aug 2012 23:51:17 +0200
Michał Górny wrote:
> But you're aware that this 'reasonable approach' just made the whole
> problem by changing exported functions, right?
No, what made the whole problem is awful eclasses that do far too many
things.
--
Ciaran McCreesh
signature.asc
Descri
On Tue, 14 Aug 2012 14:09:17 -0700
Zac Medico wrote:
> On 08/14/2012 01:54 PM, Michał Górny wrote:
> > On Tue, 14 Aug 2012 21:45:56 +0100
> > Ciaran McCreesh wrote:
> >
> >> On Tue, 14 Aug 2012 11:44:49 +0200
> >> Michał Górny wrote:
> >>> As some of you may have noticed, lately introduced 'do
On Tue, 14 Aug 2012 23:01:05 +0200
hasufell wrote:
> On 08/14/2012 10:56 PM, Ciaran McCreesh wrote:
> >
> > We can't change inherit behaviour in EAPI 5 anyway since it's a
> > global scope function, so I was planning to ignore it and hope that
> > by the time EAPI 6 comes along, people will have
On Tue, 14 Aug 2012 23:09:55 +0200
Michał Górny wrote:
> > We can't change inherit behaviour in EAPI 5 anyway since it's a
> > global scope function, so I was planning to ignore it and hope that
> > by the time EAPI 6 comes along, people will have learned not to
> > write huge eclasses that do mor
On Tue, 14 Aug 2012 21:56:38 +0100
Ciaran McCreesh wrote:
> On Tue, 14 Aug 2012 22:54:13 +0200
> Michał Górny wrote:
> > On Tue, 14 Aug 2012 21:45:56 +0100
> > Ciaran McCreesh wrote:
> > > On Tue, 14 Aug 2012 11:44:49 +0200
> > > Michał Górny wrote:
> > > > As some of you may have noticed, lat
On 08/14/2012 01:54 PM, Michał Górny wrote:
> On Tue, 14 Aug 2012 21:45:56 +0100
> Ciaran McCreesh wrote:
>
>> On Tue, 14 Aug 2012 11:44:49 +0200
>> Michał Górny wrote:
>>> As some of you may have noticed, lately introduced 'double include
>>> preventions' have caused changes in effective phase
On 08/14/2012 10:56 PM, Ciaran McCreesh wrote:
>
> We can't change inherit behaviour in EAPI 5 anyway since it's a
> global scope function, so I was planning to ignore it and hope that
> by the time EAPI 6 comes along, people will have learned not to
> write huge eclasses that do more than one thi
On Tue, 14 Aug 2012 22:54:13 +0200
Michał Górny wrote:
> On Tue, 14 Aug 2012 21:45:56 +0100
> Ciaran McCreesh wrote:
> > On Tue, 14 Aug 2012 11:44:49 +0200
> > Michał Górny wrote:
> > > As some of you may have noticed, lately introduced 'double include
> > > preventions' have caused changes in e
On Tue, 14 Aug 2012 21:45:56 +0100
Ciaran McCreesh wrote:
> On Tue, 14 Aug 2012 11:44:49 +0200
> Michał Górny wrote:
> > As some of you may have noticed, lately introduced 'double include
> > preventions' have caused changes in effective phase functions in a
> > few ebuilds. Also, often it is un
On Tue, 14 Aug 2012 11:44:49 +0200
Michał Górny wrote:
> As some of you may have noticed, lately introduced 'double include
> preventions' have caused changes in effective phase functions in a few
> ebuilds. Also, often it is undesirable that change in inherits of
> an eclass may cause an undesire
On Tue, 14 Aug 2012 12:46:30 -0700
Zac Medico wrote:
> On 08/14/2012 02:44 AM, Michał Górny wrote:
> > Hello,
> >
> > As some of you may have noticed, lately introduced 'double include
> > preventions' have caused changes in effective phase functions in a
> > few ebuilds.
>
> Can't that be avoi
On 08/14/2012 02:44 AM, Michał Górny wrote:
> Hello,
>
> As some of you may have noticed, lately introduced 'double include
> preventions' have caused changes in effective phase functions in a few
> ebuilds.
Can't that be avoided by putting the EXPORT_FUNCTIONS call outside of
the ifndef block? T
Hello,
As some of you may have noticed, lately introduced 'double include
preventions' have caused changes in effective phase functions in a few
ebuilds. Also, often it is undesirable that change in inherits of
an eclass may cause an undesired change of exported functions. To solve
these problems,
16 matches
Mail list logo
