Petteri Räty wrote:
> I suggest that we dedicate the next bugday in March to migrating as many
> built_with_use calls to use dependencies as possible. Actively
> maintained packages should have mostly been migrated by now and in
> general it's better for the user experience to get rid of all those
On Sonntag, 22. Februar 2009, Tomáš Chvátal wrote:
> Well that is the reason why i am first eapi2ing the kde eclass. I was
> really suprised when i saw kde3 ebuilds with eapi2 :(
I value users suffering from package manager issues higher and fix issues as I
see them, walking through the tree. Onl
On Sonntag, 22. Februar 2009, Petteri Räty wrote:
> Even if the eclasses are not EAPI 2 ready you can work
> around it in the ebuild by for example those empty functions.
This is fine with me, when you care for said packages and their eclasses and
know for sure such hacks have a very limited life
Carsten Lohrke wrote:
> On Freitag, 20. Februar 2009, Petteri Räty wrote:
>> Suggestions/objections?
>
> If you mean by "mass migration" doing that more or less blindly, I do object.
> When an ebuild directly or indirectly inherits an eclass, which is EAPI 2
> enabled, like base.eclass, while an
Dne neděle 22 Únor 2009 22:34:19
> Carsten Lohrke wrote:
> On Freitag, 20. Februar 2009, Petteri Räty wrote:
> > Suggestions/objections?
>
> If you mean by "mass migration" doing that more or less blindly, I do
> object. When an ebuild directly or indirectly inherits an eclass, which is
> EAPI 2 en
On Freitag, 20. Februar 2009, Petteri Räty wrote:
> Suggestions/objections?
If you mean by "mass migration" doing that more or less blindly, I do object.
When an ebuild directly or indirectly inherits an eclass, which is EAPI 2
enabled, like base.eclass, while another isn't, you have to expect
I suggest that we dedicate the next bugday in March to migrating as many
built_with_use calls to use dependencies as possible. Actively
maintained packages should have mostly been migrated by now and in
general it's better for the user experience to get rid of all those
built_with_use calls instead
