Difference between revisions of "Glossary"
| Line 3: | Line 3: | ||
'''CPAM:''' Cross-Platform Application Management, a solution to enable easy and consistent application management. TWW's HPMS is one of the solutions. | '''CPAM:''' Cross-Platform Application Management, a solution to enable easy and consistent application management. TWW's HPMS is one of the solutions. | ||
| − | '''PMS:''' Package Management System. Examples: RPM | + | '''PMS:''' Package Management System. Examples: RPM,dpkg,inst,lpp,portage,Installsield,HP SD-UX. |
| + | '''PMS format:''' PMS Package Format. A file or directory to host a group of compiled binaries ,documenation or script file. This file is usually call a software pacakge. With this work done, a softare package can be better maintained. Example formats:rpm,msi,exe,ipk,pkgadd,depot. | ||
| − | '''HPMS:''' Hyper Package Management System. A PMS above different PMSs and shield package developer from local PMS to | + | '''HPMS:''' Hyper Package Management System. A PMS above different PMSs and shield package developer from local PMS. It will allow package developer to consistently create and maintain software packages with out knowing the detail of each PMS. |
Revision as of 18:11, 16 February 2005
CPAD: Cross-Plaform Application Development, a solution to enable software application developement easily for man-made imcompatiable different operating systems. Java,OpenStep and GNUstep are three example solutions.
CPAM: Cross-Platform Application Management, a solution to enable easy and consistent application management. TWW's HPMS is one of the solutions.
PMS: Package Management System. Examples: RPM,dpkg,inst,lpp,portage,Installsield,HP SD-UX. PMS format: PMS Package Format. A file or directory to host a group of compiled binaries ,documenation or script file. This file is usually call a software pacakge. With this work done, a softare package can be better maintained. Example formats:rpm,msi,exe,ipk,pkgadd,depot.
HPMS: Hyper Package Management System. A PMS above different PMSs and shield package developer from local PMS. It will allow package developer to consistently create and maintain software packages with out knowing the detail of each PMS.