>This community is dedicated to technologies and processes related to >installing and >maintaining software on OpenSolaris-based disributions, including tools used >in building distributions.
>While the community is home to the SVR4 packaging tools project, which are the >tools included in the Solaris product and some other OpenSolaris-based >distributions, >we also welcome discussion (and projects) related to other packaging >technologies. Hi all Since other packaging technologies are also welcome so it is me again, the HPMS guy ;) As a spare time activity, I like to promote using proxy(hyper) package management system to do the SVR4 packaing. I am aware of sunfreeware.com, blastwave.org and openpkg.org and Nexenta(debian) packaging methodologies. If these methodologies work for you then stop reading. discard this thread to save your some time. I have been using TWW's tool doing packages for Solaris and other OS for last few years. I believe this is cool technology. T1 Sparc CPU is been promoted as a green technology becuause it consume less Earth Resources to generate power tht CPU needed. I think TWW HPMS is another similar green technology to consume less packaging brain power to generate SVR4 packages for O.S. community. Above packaging methodologies for Solaris don't work for me. Why ? Expection 1: Digitation I like to have automated packaging system to generate packages like programmer/developer digitalize their logic/knowhow into a makefiles. "cd perl-5.6.1;./configure;make;make install" or "make perl-5.6.1" only deliver perl-5.6.1 interpretor under /usr/local/bin/(assumed). This automation only upto binary level, no package. With TWW HPMS, we can do "make perl-5.6.1 upload=1", a perl-5.6.1 Solaris SVR4 package will be configured,compiled,packaged and uploaded to application depot server. if the there is no error durning the software compiling, packaging making process. How do you implement /usr/local/bin/perl ?, We all know go read the perl C source codes. The C source codes describe how scanner,parser and other functions got implemented to have perl function as programming language interpretor. But how do you build perl-5.6.1 and package it ? Is there a software/package build source codes that I can repeat with command instead of reading English in text files ? or asking question on email on how to compile perl ? If someone already there and done the correct configuration to get perl-5.6-1 compiled and packaged , can we have that process digitalize into source code that can be repeated by easy command ? Expection 2: Simple I want to be able to install a package by one command, all the depended other software should be install automatically also. Expection 3: Reuse packaging effort across OS platforms. I want to compose one package source and use it to generate packge for other PMS packages. ie for perl-5.6.1 software I want one package source to generate rpm,pkgadd,depot,inst, lpp or even win32 MSI or Mac OS X .app. Expection 4: Non-intrusive Retring existing packaging solution is very costly or impossible mission in an IT. I like to have a hybrid packaing solution. TWW HPMS is only methodology that meet my greedy(?) expectation. I am glad we have this community for me to promote my believe. I don't want spend my time on debating which PMS is better and such. I am interested to know how we can team up our efforts by using TWW HPMS. Doing things alone is always a heavy weight to carry. So if you are interested to help please follow up to this thread. I once contacted owners of sunfreeware.com and blastwave.org for chance of teaming up the effort. but I must done a vey poor sales job or we have different packaging belief. that is fine too. We all have right to pursure our own believe. Done talking and thinking. Plan for action, TBA in coming post. tj References: 1. http://www.thewrittenword.com 2. http://en.wikibooks.org/wiki/User:Tjyang -- This messages posted from opensolaris.org
