[prev in list] [next in list] [prev in thread] [next in thread] 

List:       aix-l
Subject:    Re: AIX lpp creation
From:       "Mills, John T" <John.Mills () GRAYBAR ! COM>
Date:       2010-02-09 18:09:51
Message-ID: AAE7A39506A54244BEB5A08D5973CE842ABBB5ABCD () SEMBV1PW ! graybar ! com
[Download RAW message or body]

You can't do a question in the installp.  It's a bit odd.  It locks the server from \
additional installp's during the execution, and, it isn't interactive.  What you \
should do is provide a small config file that the package will look for.  If the \
config file's there, it would pull in the user responses.  If it is not found it \
could fail to install with a banner error or use defaults.

John T Mills

________________________________
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of Justin \
                Bleistein
Sent: Tuesday, February 09, 2010 10:41 AM
To: aix-l@Princeton.EDU
Subject: Re: AIX lpp creation

Thanks for your response. I looked through this stuff, and all is starting to come \
together. One thing I can't seem to figure out, and documentation out on google seems \
to be limited on this topic. When my users run the installp command to install my \
software I would like the installp command smit, or command line to prompt the users \
running that installp command for configuration information about my software they \
are installing. I created a software package in solaris, and there was somethnig \
called a request script that would be called from the pkgadd command. The request \
script was the only location where I could have called read korn shell statements, \
causing my scripts being called by pkgadd, to request input from the users. I put a \
read statement in the pre_i script for instance, and installp executes the script, \
but just blows right by the read input prompt.

Any ideas?
Thanks in advance.

Justin Richard Bleistein | AIX System Administration
________________________________
From: IBM AIX Discussion List [aix-l@Princeton.EDU] On Behalf Of Mills, John T \
                [John.Mills@GRAYBAR.COM]
Sent: Tuesday, February 09, 2010 8:13 AM
To: aix-l@Princeton.EDU
Subject: Re: AIX lpp creation

Here's what I use.  It's just a series of scripts, so, if you wanted to pick it apart \
its all in there.  I like this one because I can do a package in about 5 minutes.  \
Sun's, IBM's, and Linux's methods take me longer unless there is a package I can \
clone.

John T Mills

===============================================
Where can I get mklpp?
===============================================
Try BULL: http://www-frec.bull.com/

It was in: http://www.bullfreeware.com/listaix51.html

Their latest is bull.mklpp-1.2.9.0, February 16 2001.

It's a script. Don't worry about versions.

I hack my version and repackage it with itself when I'm done. Things can be changed \
in this fashion like:

    * Install location
    * package prefix
    * comments for ease of use
    * additional requirements specific to you

===============================================
Using mklpp to create BFF packages for installp
===============================================
Compile/collect code for packaging:

./configure
make
make install
cd /
tar cvf /tmp/pkg.tar ./newly/compiled/pkg

===============================================
Use:
===============================================
cd to working directory of your choice
newlpp <pkgdir> <newpkg>
cd <pkgdir>
touch .info/copyright
edit lpp_name
   change version from 00.00.0000.0000 to 1.0.0.0 (Don't set this to the binary \
version)  change "newpkg pre-compiled utility" to something desciptive ie "NewPKG \
<binary version> - comment"  add prerequisite fileset(s) between "[" and "%" \
immediately after the version line:  [
         *prereq freeware.<otherpkg>.rte 1.0.0.1
         *prereq freeware.<nextpkg>.rte
         %
tar xvf /tmp/pkg.tar
mklpp
edit the end of .info/*.pre_i to add additional scripts/commands to pre-installation
edit the end of .info/*.post_i to add additional scripts/commands to \
post-installation  Use mklinks.ksh if you have many files to link. (ie OpenSSL man \
pages) edit the end of .info/*.unpost_i to add additional scripts/commands to \
post-uninstallation  Use rmlinks.ksh if you have many files to unlink. (ie OpenSSL \
man pages) mklpp

===============================================
Test:
===============================================
1. Clean installation

2. Upgrade

3. Overwrite installation

4. Uninstallation, followed by clean installation


________________________________
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of Justin \
                Bleistein
Sent: Monday, February 08, 2010 2:32 PM
To: aix-l@Princeton.EDU
Subject: AIX lpp creation

Hi all,

       I found documentation on the mkinstallp command which comes with the \
bos.adt.inst fileset in AIX to create your own software packages in AIX to be \
installed with the installp command. I installed this fileset, and used the \
mkinstallp script just fine. My issue though is in the AIX programming guide out on \
the Information center states that there are ALOT of options when creating a software \
package, but the mkinstallp command doesn't prompt me for all of that information \
when I run it. Does anyone have the manual procedure for creating packages without \
the mkinstallp command?

Let me know.
Thanks in advance.

Justin Richard Bleistein | AIX System Administration


[Attachment #3 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE title=owaParaStyle><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></STYLE>

<META content="MSHTML 6.00.2900.3660" name=GENERATOR></HEAD>
<BODY ocsi="x">
<DIV dir=ltr align=left><SPAN class=745060618-09022010><FONT face="Courier New" 
size=2>You can't do a question in the installp.&nbsp; It's a bit odd.&nbsp; It 
locks the server from additional installp's during the execution, and, it isn't 
interactive.&nbsp; What you should do is provide a small config file that the 
package will look for.&nbsp; If the config file's there, it would pull in the 
user responses.&nbsp; If it is not found it could fail to install with a banner 
error or use defaults.</FONT></SPAN></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=745060618-09022010><FONT face="Courier New" size=2>John T 
Mills</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> IBM AIX Discussion List 
[mailto:aix-l@Princeton.EDU] <B>On Behalf Of </B>Justin 
Bleistein<BR><B>Sent:</B> Tuesday, February 09, 2010 10:41 AM<BR><B>To:</B> 
aix-l@Princeton.EDU<BR><B>Subject:</B> Re: AIX lpp creation<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr><FONT face=Tahoma size=2>Thanks for your response. I looked through 
this stuff, and all is starting to come together.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2>One thing I can't seem to figure out, and 
documentation out on google seems to be limited on this topic.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2>When my users run the installp command to 
install my software I would like the installp command smit, or command line to 
prompt the users running that installp command for configuration</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2>information about my software they are 
installing. I created a software package in solaris, and there was somethnig 
called a request script that would be called from the pkgadd command. 
</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2>The request script was the only location 
where I could have called read korn shell statements, causing my scripts being 
called by pkgadd, to request input from the users. I put a read statement in 
the</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2>pre_i script for instance, and installp 
executes the script, but just blows right by the read input prompt.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=tahoma size=2>Any ideas?</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2>Thanks in advance.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT size=2><SPAN 
style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: 'Verdana','sans-serif'">Justin 
Richard Bleistein&nbsp;</SPAN><SPAN 
style="FONT-SIZE: 7.5pt; COLOR: #ff9900; FONT-FAMILY: \
'Verdana','sans-serif'">|</SPAN><SPAN  style="FONT-SIZE: 7.5pt; COLOR: navy; \
FONT-FAMILY: 'Verdana','sans-serif'">&nbsp;AIX&nbsp;System&nbsp;Administration</SPAN></FONT> \


<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> IBM AIX Discussion List 
[aix-l@Princeton.EDU] On Behalf Of Mills, John T 
[John.Mills@GRAYBAR.COM]<BR><B>Sent:</B> Tuesday, February 09, 2010 8:13 
AM<BR><B>To:</B> aix-l@Princeton.EDU<BR><B>Subject:</B> Re: AIX lpp 
creation<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2><SPAN 
class=907510813-09022010>Here's what I use.&nbsp; It's just a series of scripts, 
so, if you wanted to pick it apart its all in there.&nbsp; I like this one 
because I can do a package in about 5 minutes.&nbsp; Sun's, IBM's, 
and&nbsp;Linux's methods&nbsp;take me longer unless there is a package I can 
clone.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2><SPAN 
class=907510813-09022010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2><SPAN 
class=907510813-09022010>John T Mills</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2><SPAN 
class=907510813-09022010><FONT face="Courier New" 
size=2>===============================================</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>Where can I get 
mklpp?</FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN class=907510813-09022010><FONT 
face="Courier New" 
size=2>===============================================</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>Try BULL: <A 
href="http://www-frec.bull.com/" 
target=_blank>http://www-frec.bull.com/</A></FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>It was in: <A 
href="http://www.bullfreeware.com/listaix51.html" 
target=_blank>http://www.bullfreeware.com/listaix51.html</A></FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>Their latest is 
bull.mklpp-1.2.9.0, February 16 2001.</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>It's a script. Don't 
worry about versions.</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>I hack my version and 
repackage it with itself when I'm done. Things can be changed in this fashion 
like:</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>&nbsp;&nbsp;&nbsp; * 
Install location<BR>&nbsp;&nbsp;&nbsp; * package prefix<BR>&nbsp;&nbsp;&nbsp; * 
comments for ease of use<BR>&nbsp;&nbsp;&nbsp; * additional requirements 
specific to you </FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=907510813-09022010><FONT face="Courier New" 
size=2>===============================================</FONT></SPAN><BR><FONT 
face="Courier New" size=2>Using mklpp to create BFF packages for 
installp</FONT></DIV>
<DIV><SPAN class=907510813-09022010><FONT face="Courier New" 
size=2>===============================================</FONT></SPAN></DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>Compile/collect code for 
packaging: </FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" 
size=2>./configure<BR>make<BR>make install<BR>cd /<BR>tar cvf /tmp/pkg.tar 
./newly/compiled/pkg</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2></FONT><SPAN 
class=907510813-09022010><FONT face="Courier New" 
size=2>===============================================</FONT></SPAN><BR><FONT 
face="Courier New" size=2>Use: </FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN class=907510813-09022010><FONT 
face="Courier New" 
size=2>===============================================</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>cd to working directory 
of your choice<BR>newlpp &lt;pkgdir&gt; &lt;newpkg&gt;<BR>cd 
&lt;pkgdir&gt;<BR>touch .info/copyright<BR>edit lpp_name<BR>&nbsp;&nbsp; change 
version from 00.00.0000.0000 to 1.0.0.0 (Don't set this to the binary 
version)<BR>&nbsp;&nbsp; change "newpkg pre-compiled utility" to something 
desciptive ie "NewPKG &lt;binary version&gt; - comment"<BR>&nbsp;&nbsp; add 
prerequisite fileset(s) between "[" and "%" immediately after the version 
line:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
[<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *prereq 
freeware.&lt;otherpkg&gt;.rte 
1.0.0.1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *prereq 
freeware.&lt;nextpkg&gt;.rte<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
%<BR>tar xvf /tmp/pkg.tar<BR>mklpp<BR>edit the end of .info/*.pre_i to add 
additional scripts/commands to pre-installation<BR>edit the end of 
.info/*.post_i to add additional scripts/commands to 
post-installation<BR>&nbsp;&nbsp; Use mklinks.ksh if you have many files to 
link. (ie OpenSSL man pages)<BR>edit the end of .info/*.unpost_i to add 
additional scripts/commands to post-uninstallation<BR>&nbsp;&nbsp; Use 
rmlinks.ksh if you have many files to unlink. (ie OpenSSL man 
pages)<BR>mklpp</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2></FONT><SPAN 
class=907510813-09022010><FONT face="Courier New" 
size=2>===============================================</FONT></SPAN><BR><FONT 
face="Courier New" size=2>Test: </FONT></DIV>
<DIV><FONT face="Courier New" size=2><SPAN class=907510813-09022010><FONT 
face="Courier New" 
size=2>===============================================</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>1. Clean installation 
</FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>2. Upgrade </FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>3. Overwrite 
installation </FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT face="Courier New" size=2>4. Uninstallation, 
followed by clean installation </FONT></DIV>
<DIV><FONT face="Courier New" size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> IBM AIX Discussion List 
[mailto:aix-l@Princeton.EDU] <B>On Behalf Of </B>Justin 
Bleistein<BR><B>Sent:</B> Monday, February 08, 2010 2:32 PM<BR><B>To:</B> 
aix-l@Princeton.EDU<BR><B>Subject:</B> AIX lpp creation<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr><FONT face=Tahoma size=2>Hi all,</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=tahoma size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I 
found documentation on the mkinstallp command which comes with the bos.adt.inst 
fileset in AIX to create your own software packages in AIX to be installed with 
the installp command. I installed this fileset, and used the mkinstallp script 
just fine. My issue though is in the AIX programming guide out on the 
Information center states that there are ALOT of options when creating a 
software package, but the mkinstallp command doesn't prompt me for all of that 
information when I run it. Does anyone have the manual procedure for creating 
packages without the mkinstallp command?</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT>&nbsp;</DIV>
<DIV dir=ltr><FONT face=tahoma size=2>Let me know.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2>Thanks in advance.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT>&nbsp;</DIV>
<DIV class=BodyFragment><FONT size=2>
<DIV class=PlainText><SPAN 
style="FONT-SIZE: 7.5pt; COLOR: navy; FONT-FAMILY: 'Verdana','sans-serif'">Justin 
Richard Bleistein&nbsp;</SPAN><SPAN 
style="FONT-SIZE: 7.5pt; COLOR: #ff9900; FONT-FAMILY: \
'Verdana','sans-serif'">|</SPAN><SPAN  style="FONT-SIZE: 7.5pt; COLOR: navy; \
FONT-FAMILY: 'Verdana','sans-serif'">&nbsp;AIX&nbsp;System&nbsp;Administration&nbsp;</SPAN></DIV></FONT></DIV></DIV></BODY></HTML>




[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic