1 |
On Sat, 16 Jan 2010 15:29:48 +0200 |
2 |
Petteri Räty <betelgeuse@g.o> wrote: |
3 |
|
4 |
> On 01/12/2010 12:23 AM, Brian Harring wrote: |
5 |
> > On Mon, Jan 11, 2010 at 09:25:51PM +0100, Raaal Porcel wrote: |
6 |
> >> scarabeus told me that the eclass can't be removed until two years since |
7 |
> >> the deprecation date, so... |
8 |
> >> |
9 |
> >> Removal of the eclass on 2012/01/11 |
10 |
> > |
11 |
> > Reasoning? Prior to env saving we couldn't particularly punt |
12 |
> > eclasses, but env saving is widely deployed now... |
13 |
> > |
14 |
> > ~harring |
15 |
> |
16 |
> At least my argument at the time was that better to be safe when the |
17 |
> benefit from removing old eclasses isn't that much. |
18 |
|
19 |
Still, waiting another two years to be able to remove an eclass which |
20 |
itself hasn't been used in two years seems a little ridiculous. I can see |
21 |
waiting two years from when env saving went into stable, but that's passed |
22 |
already. |
23 |
|
24 |
wxlib.eclass was recently removed (accidentally) after being |
25 |
deprecated for just a couple months, and the world continued to revolve |
26 |
despite it. ;) |
27 |
|
28 |
|
29 |
-- |
30 |
fonts, looks like Christmas at 55 degrees |
31 |
gcc-porting, this latitude weakens my knees |
32 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |