Message-ID: <3D80854A.BA8E7322@lml.ls.fi.upm.es> Date: Thu, 12 Sep 2002 14:15:06 +0200 From: Manuel Collado X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: List of DJGPP packages References: <3D7735B1 DOT F752E6DA AT lml DOT ls DOT fi DOT upm DOT es> <200209071414 DOT g87EEPV13625 AT envy DOT delorie DOT com> <3D7DD581 DOT CAD1BBE7 AT lml DOT ls DOT fi DOT upm DOT es> <3D7E54C9 DOT 593DC70F AT phekda DOT freeserve DOT co DOT uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 138.100.10.20 X-Trace: 12 Sep 2002 14:16:33 +0100, 138.100.10.20 Lines: 39 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Richard Dawe wrote: > [snip] > One solution to this problem is to write DSMs for all the legacy packages and > put them in a package, e.g.: djgpp-legacy-dsms. pakke actually comes with DSMs > for some legacy packages. I wasn't aware of that. I'm rebuilding the package list by using also data from these dsms. In doing so, I've collected the present status of dms availability: Folder Listed Internal-dsm External-dsm With-dsm Without-dsm (1) (2) (3) (4) (5) ------------ -------- ------------ ------------ -------- ----------- v2 20 9 6 15 5 v2apps 82 14 8 22 60 v2apps/tex 38 2 36 38 0 v2gnu 308 141 45 186 122 v2misc 35 4 5 9 26 v2tk 108 12 4 16 92 v2tk/allegro 36 0 0 0 36 Total 627 182 104 286 341 (46%) (54%) (1) Listed in 00_index.txt (2) The .zip archive contains a dsm file (3) No dsm inside .zip, but there is one in pakke database (4) = (2) + (3) (5) = (1) - (4) Roughly, half the package archives already have dsms, and figures are better if we consider only the most recent version of each package. With some (hopefuly moderate) effort, minimal dsms could be build for every remaining package. -- To reply by e-mail, please remove the extra dot in the given address: m.collado -> mcollado