* T.J. Yang <[EMAIL PROTECTED]> [050919 18:49]: > >From: [EMAIL PROTECTED]
> >> Also Schillix LiveCD project won't need to develop yet another PMS, SPS. > >We actualy do not try to implement a PMS. We implement a build system > >mostly, which could be used together whith SVR4 PMS. But right now we > >use a "better" tar version. > > Ok, then SPS is in the catergory of HPMS. a system sit on top of > existing PMS and interact with existing PMS to do the package > mangement tasks like install,remove,upgrade,packaging etc. The > modern PMS support not just install, they support auto install, remove > package base on package's dependency. I have to contradict you here. SPS is not in the catergory of an HPMS. As far as I understood your text[1] an HPMS shields the user from using the underlaying PMS. SPS is *only* a build system. Actlualy its a derived version of Joergs build system for his own tools. (smake, star,....) But in the near future it is possible to create packages. Right now it builds tar archives, controled by meta data given by the package author. Though calling `make install` will install the compiled programs to an changeable system path (/usr/sps). [1]: http://en.wikibooks.org/wiki/CPAM_with_TWW/User_Guide#Acronyms:_CPAD.2C_CPAM.2C_PMS.2C_HPMS_and_TWW > Otto, I like to invite you to take a look at TWW HPMS and OSMOT that > has /opt/moto installation path. I belive SPS or pkg-get try to > achieve are all implemented by TWW's HPMS. Since I get payed for developing packages (Makefiles mostly) for SPS, i can not follow your invitation *at work. But I started recently to maintain an Ultra 10 with OSEXC nv19. It seems to me a perfect place to form an educated opinion about TWW. > tj Otto _______________________________________________ opensolaris-discuss mailing list [email protected]
