Re: [Freedos-devel] Installed Application Database Hypothesis
I was thinking Perl (or awk) for the line processing to remove lines because you may install a lot of apps in between the one you want to delete. -T - Original Message - From: "Eric Auer" <[EMAIL PROTECTED]> To: Sent: Wednesday, January 09, 2008 10:36 AM Subject: Re: [Freedos-devel] Installed Application Database Hypothesis > > Hi Antony (please use plain text mail without html!), > >> Implementing an Installed Application Database along with an associated >> install API would make installing applications easier (perhaps somewhat >> akin to Windows). > > There is not an API but a tool. We do have that tool. It does have an > installed application database, too. > >> Each application comes packaged in a ZIP file that contains a text file >> with a list of conflicting applications, prerequisite applications, and >> suggested configuration settings/memory requirements. Does the present >> installer have a means of locating said conflicting applications and >> checking prerequisites? > > Yes it does. > >> Nothing overly complex, but perhaps a flat file database that can list >> applications as they are installed. I looked at the INSTALL.LOG file and >> the options of FDPKG. What I would be suggesting would be something >> along these lines > > I believe FDPKG has an option "list installed applications". > This option basically gives you a directory listing of LSM > files, along with selected lines from those files ;-). > >> Currently installed packages/applications >>+ FreeDOS 1.0 >>+ FreeDOS GEM >>+ Random Application >> Use arrow keys to select pages > ... >>Change/Remove Application (existing apps on the computer) >>Install New Program (even if...) > > Sounds complicated to track non freedos apps. Would be > better to do this manually. If you download a foreign > zip and unzip it, you will very often rename and move > files manually after unzipping. > >>Add/Remove FreeDOS components (Devel tools, Language support, etc) >> Options Menu >>Tracking (track 3rd party installs on/off) >> Basically log the changes each install makes to config autoexec >> to facilitate easier removal (basically makes a copy before install >> and creates a DIFF file) > ... > >> I think the hardest part would be tracking the changes on >> autoexec/config which I think would require PERL or awk to >> process. > > The whole project can be pretty complex. It would be a mix of > the existing TEXTINST, the existing FDPKG and maybe FDUPDATE, > some nice user interface and several new things. You do not > need Perl (but there is Perl for DOS) if you only want to run > DIFF :-). > > Eric > > > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Installed Application Database Hypothesis
Hi Antony (please use plain text mail without html!), > Implementing an Installed Application Database along with an associated > install API would make installing applications easier (perhaps somewhat > akin to Windows). There is not an API but a tool. We do have that tool. It does have an installed application database, too. > Each application comes packaged in a ZIP file that contains a text file > with a list of conflicting applications, prerequisite applications, and > suggested configuration settings/memory requirements. Does the present > installer have a means of locating said conflicting applications and > checking prerequisites? Yes it does. > Nothing overly complex, but perhaps a flat file database that can list > applications as they are installed. I looked at the INSTALL.LOG file and > the options of FDPKG. What I would be suggesting would be something > along these lines I believe FDPKG has an option "list installed applications". This option basically gives you a directory listing of LSM files, along with selected lines from those files ;-). > Currently installed packages/applications >+ FreeDOS 1.0 >+ FreeDOS GEM >+ Random Application > Use arrow keys to select pages ... >Change/Remove Application (existing apps on the computer) >Install New Program (even if...) Sounds complicated to track non freedos apps. Would be better to do this manually. If you download a foreign zip and unzip it, you will very often rename and move files manually after unzipping. >Add/Remove FreeDOS components (Devel tools, Language support, etc) > Options Menu >Tracking (track 3rd party installs on/off) > Basically log the changes each install makes to config autoexec > to facilitate easier removal (basically makes a copy before install > and creates a DIFF file) ... > I think the hardest part would be tracking the changes on > autoexec/config which I think would require PERL or awk to > process. The whole project can be pretty complex. It would be a mix of the existing TEXTINST, the existing FDPKG and maybe FDUPDATE, some nice user interface and several new things. You do not need Perl (but there is Perl for DOS) if you only want to run DIFF :-). Eric - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Installed Application Database Hypothesis
Hypothesis: Implementing an Installed Application Database along with an associated install API would make installing applications easier (perhaps somewhat akin to Windows). What I've learned: Each application comes packaged in a ZIP file that contains a text file with a list of conflicting applications, prerequisite applications, and suggested configuration settings/memory requirements. Does the present installer have a means of locating said conflicting applications and checking prerequisites? What I am suggesting: Nothing overly complex, but perhaps a flat file database that can list applications as they are installed. I looked at the INSTALL.LOG file and the options of FDPKG. What I would be suggesting would be something along these lines C:\>PKGMGR < just chose that since FDPKG was in use FreeDOS Package Manager v x.xx File Maintenance Options Help Currently installed packages/applications + FreeDOS 1.0 + FreeDOS GEM < repackaged for PKGMGR but basically Shane's OpenGEM + Random Application Use arrow keys to select pages File Menu Exit (Obvious) Maintenance Menu Change/Remove Application (existing apps on the computer) Install New Program (even if it is not a PKGMGR installer, this can track the changes for later removal) Add/Remove FreeDOS components (Devel tools, Language support, etc) Options Menu Tracking (track 3rd party installs on/off) Basically log the changes each install makes to config.sys autoexec.bat to facilitate easier removal (basically makes a copy before install and creates a DIFF file) Help Menu Self explanatory I think the hardest part would be tracking the changes on autoexec.bat/config.sys which I think would require PERL or awk to process. _ Share life as it happens with the new Windows Live. http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
