Re: [Freedos-devel] FreeDOS LSM and fdupdate inventory issues
Hi, I would say fdpkg is the more complete package management frontend, so if you want to modify one to make the other obsolete, you should instead add fdupdate functionality to fdpkg ;-). But for me, it is fine to have both fdpkg and fdupdate. The latter could make more use of fdpkg, that would make the fdupdate part simpler so it could focus on other things... Eric Geraldo wrote: > i would suggest to extend fdupdate as freedos main pkg front end > all we need to do is add the possibility to create local repos > i mean, be able to use cd, floppy or whatever as a repo :) > and of course still use fdpkg and back end... -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS LSM and fdupdate inventory issues
Hi, i would suggest to extend fdupdate as freedos main pkg front end all we need to do is add the possibility to create local repos i mean, be able to use cd, floppy or whatever as a repo :) and of course still use fdpkg and back end... Geraldo Sapere Aude Non ducor, duco São Paulo, Brasil, -3gmt site: http://exdev.sf.net/ msn: geraldo_boca_at_hotmail.com skype: geraldo-netto icq: 145-061-456 2009/1/3 Mateusz Viste : > On Monday 22 December 2008 23:49, Jim Hall wrote: >> I think it's better to keep them separate. I like that FDUPDATE only >> does one thing - download updates. FDPKG is pretty mature, and should >> remain the package manager. To try to push that functionality into >> FDUPDATE at this time would risk adding too many bugs. > > Basically I agree with you, Jim. > However, it's important to note that FDUPDATE is not only an updater, it may > install new software from online repositories, too :-) > > In any case, it should be perceived as an network tool, and it *requires* > FDPKG anyway, as the whole "remove/install/update stuff" work is done > externally by FDPKG, not by FDUPDATE (FDUPDATE acts just as a wrapper then). > > Best regards, > Mateusz V. > -- > You'll find my public OpenPGP key at > http://www.viste-family.net/mateusz/pub_key > -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS LSM and fdupdate inventory issues
Hi guys! How are you doing there? First of all, if we do not exchange emails in the mean time i really wish to you all a great merry christmas/new year time! :) Folks, i think it is fine to get the list of software to update and repack it for fd 1.1 and count on me for this but i would prefer to move it to devel, what do you all think? btw, which batches need review? ah, i've done the translation of fdupdate 0.53(i guess) but it is lost somewhere in my disk... talking about fdupdate, can we make fdupdate our package manager? of course we would need to add some features, like fdupdate, been able to check local repos(for cd/floppies/usb/...) instead only "networked repos" what do you all think? Count on me for FD 1.1! Kind Regards and Best Wishes, Geraldo Sapere Aude Non ducor, duco São Paulo, Brasil, -3gmt site: http://exdev.sf.net/ msn: geraldo_boca_at_hotmail.com skype: geraldo-netto icq: 145-061-456 2008/12/19 Rugxulo : > Yo, > > On Fri, Dec 19, 2008 at 2:20 PM, Eric Auer wrote: >> >> now I have a 7zip of 1.5 MB with everything except: >> >> - the *EDLIN binary* (who has a copy of that?) > > Compiled by which compiler? (I assume OpenWatcom for the 16-bit one, > but 32-bit also compiles with others, e.g. CC386.) Lemme compile both > .EXEs via OpenWatcom for you, and see what you think: > > http://rugxulo.googlepages.com/edlin-2.10c-dos.zip (.EXEs only, no > docs, no dirs, no srcs) > http://rugxulo.googlepages.com/edln210c.tbz(srcs, just to comply with GPL) > >> - the EDIT *D-FLAT library* and sources > > That's on iBiblio, of course: > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/libs/dflat/ > > There's even a readme.txt (quoted from freedos-devel) for help on > compiling HWORLD example using D-Flat: > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/libs/dflat/readme.txt > >> Please let me know if I can send you that 7zip file. >> [All except Mateusz: He already said yes I can :-)] >> >> The 7zip file contains one directory tree per package: >> >> chkdsk-0.9.1/ edlin-2.10c/gcdrom-2.4/ print-1.02/ >> comp-1.04/ fdisk-1.3.1/himemx-3.32/shsu-cd-3-2/ >> edit-0.9a/ find-3.0a-lfn/ kernel-2038-2008mar08/ shsucdx-3.04/ >> >> Simply chdir to a directory and zip everything inside >> to create a package for FDUPDATE / FDPKG / similar :-) >> >> There are no empty packages/PACKAGENAME directories, but >> feel free to add them. There are, however, empty appinfo/ >> directories in the (common) case of missing LSM files. > > Note that I think 7-Zip doesn't add empty directories to archives. > Even some unzippers have trouble with that, hence why DJGPP packages > usually have a small REMOVE.ME file (e.g. in /TMP). So be wary of > that. > >> Note: I re-UPXed some things which previously used UPX-closed >> using UPX-UCL --8086 --best (which is Ubuntu's default UPX). > > I haven't heard anything about the UPX-UCL package for FreeDOS, but I > did write a simple compilation .BAT, remember? If anybody wants it, I > can try to pack it up (but I'll admit, I'm still fairly confused by > the strict dir structure of FreeDOS packages ... BIN DOC SOURCE HELP) > in .ZIP format, which is what you seem to prefer. > > http://rugxulo.googlepages.com/upx303c.txt (it's a .BAT, actually) > >>> I checked against what's published at >>> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos ... >>> If there are any new release, just tell me where can I get them, >>> or (better) send me the updated package :) > > My list of updated packages isn't currently up-to-date (still dated > from July 2008), but that plus my web page lists everything I'm aware > of. For instance, I never heard about gcdrom 2.4, so I've never gotten > it (only got 2.3 via pointer from Eric months back). > > http://rugxulo.googlepages.com/fdpkgnew.txt > http://rugxulo.googlepages.com > > I've actually procrastinated updating that more so I could finish > other things (of course). Then again, I get no feedback about > anything, so I never know who gives a crap. ;-) > - for country, nlsfunc, cpidos, display, share, exe2bin, keyb, kpdos, fdshield and the devel/2037 kernel, release dates of FreeDOS 1.0 and package are similar: Was any of them actually released AFTER FreeDOS 1.0 / not included in FreeDOS 1.0? > > FDPKGNEW.TXT is supposed to list everything since 1.0 that I'm aware > of. So that's all I can offer. (See caveat above about being slightly > outdated.) > -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS LSM and fdupdate inventory issues
Hi Geraldo! On Mon, Dec 22, 2008 at 3:55 PM, Geraldo Netto wrote: > Hi guys! > > How are you doing there? > > First of all, if we do not exchange emails in the mean time i really > wish to you all a great merry christmas/new year time! :) Merry Christmas to you too, all of you! http://www.freedos.org/jhall/2008/12/21/merry-christmas.html :-) > talking about fdupdate, can we make fdupdate our package manager? > of course we would need to add some features, like fdupdate, been able > to check local repos(for cd/floppies/usb/...) > instead only "networked repos" > what do you all think? > I think it's better to keep them separate. I like that FDUPDATE only does one thing - download updates. FDPKG is pretty mature, and should remain the package manager. To try to push that functionality into FDUPDATE at this time would risk adding too many bugs. Anyway, I don't know that FDUPDATE has the architecture to support FDPKG functionality. -jh -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS LSM and fdupdate inventory issues
Hi everybody :-) First a correction about help.fdos.org - it does render okay in firefox, it is only outdated. Reason for the failure to display was a firefox update running exactly at the same moment... ;-). > wish to you all a great merry christmas/new year time! :) Thanks, same to you :-) > btw, which batches need review? http://fd-doc.sourceforge.net/wiki/index.php?n=FdDocEn.FdInstall?action=diff explains that, kind of. Note that the page itself is damaged by spammers and that my own spam protection prevents me from undoing the damage without using file system access, sorry. So unless you migrate that page to the sourceforge mediawiki before that, we will have to wait until next week before I can fix "FdInstall". > talking about fdupdate, can we make fdupdate our package manager? No, why should we? FDPKG already exists and works well. FDUPDATE is for updates. If you find things where one could learn from the other, you can of course suggest that FDPKG and FDUPDATE should share more code there. > Count on me for FD 1.1! Thanks :-) Eric PS: http://fd-doc.sourceforge.net/wiki/index.php?n=FdDocEn.FdDependencies is also useful, because I suggest that there should be an easy (only few keypresses) way to disable all network dependant aspects of the install, for offline installs. People can add network stuff later with FDPKG or even manually after downloading files within Windows/Linux. -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
