Mail Archives: djgpp-workers/2001/11/05/12:54:49
> And these redundancies:
>
> acnf 212 213 250
212 can go; I'd keep 213 around, as there are major changes
in 2.5x (often requiring changes to configure.in/acincude.m4/...),
so people may want to stick with 2.13.
> amake 13 14 15
Here I think 13 and 14 can both go, as 1.5 should be fully
backward compatible (and fixes a cartload of bugs).
> bsn 128 129
Not sure. 1.28 can probably go.
> cvs 110 19
Fairly sure 1.9 can go. This reminds me that I should really
put a package together for 1.11.1 (or whatever the latest version
is).
> em 1934 2005
19.34 can probably go.
Eli, is a 21.1 port on the cards?
> fil 316 40
Not sure, but 3.16 can probably go.
> gcc 2952 2953 302
May want to keep 2.95.3 in case there are issues with 3.0.
2.95.2 can probably go.
> gdb 418 500
4.18 can probably go. Eli?
> gmp 311 311x
Don't know the difference.
> gpc 20b 2953
My guess is that 2.0b is seriously outdated (gcc 2.8.1?), so I think
it can go.
> gtxt 037 039 040
I'd keep 037 around, as I think it's the last 'lightweight'
gettext (i.e. without the libiconv stuff). 039 can probably go.
> gzp 124 124a
Don't know the difference.
> ind 224 225
I expect 224 can go.
> isp 3120 3206
Not sure; 3120 can probably go.
> pat 21 253
Think 2.1 can go.
> perl 552 561
May want to keep both
This reminds me, I still need to update the updated source package I
uploaded (with a 2.04-compatible Configure). I'll do that today
(probably).
> sed 118 302 3028
1.18 can most probably go; not sure if we want/need to keep 3.0.2.
- Raw text -