<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: swinstall - passing variables to control scripts in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002798#M126859</link>
    <description>Hello!&lt;BR /&gt;&lt;BR /&gt;Generate dinamicly your sw scripts with&lt;BR /&gt;the wanted variables.&lt;BR /&gt;Or your sw scripts can read some config&lt;BR /&gt;file which will have the variables.&lt;BR /&gt;&lt;BR /&gt;Caesar</description>
    <pubDate>Thu, 19 Jun 2003 19:55:20 GMT</pubDate>
    <dc:creator>Caesar_3</dc:creator>
    <dc:date>2003-06-19T19:55:20Z</dc:date>
    <item>
      <title>swinstall - passing variables to control scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002797#M126858</link>
      <description>I have an in-house application for which I'm creating a depot.  There are pre-defined internal variables usable by the control scripts.  How can I store a variable that stays with the package for use within the config or checkinstall scripts?</description>
      <pubDate>Thu, 19 Jun 2003 19:50:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002797#M126858</guid>
      <dc:creator>Mike McDevitt</dc:creator>
      <dc:date>2003-06-19T19:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall - passing variables to control scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002798#M126859</link>
      <description>Hello!&lt;BR /&gt;&lt;BR /&gt;Generate dinamicly your sw scripts with&lt;BR /&gt;the wanted variables.&lt;BR /&gt;Or your sw scripts can read some config&lt;BR /&gt;file which will have the variables.&lt;BR /&gt;&lt;BR /&gt;Caesar</description>
      <pubDate>Thu, 19 Jun 2003 19:55:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002798#M126859</guid>
      <dc:creator>Caesar_3</dc:creator>
      <dc:date>2003-06-19T19:55:20Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall - passing variables to control scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002799#M126860</link>
      <description>Hi Mike,&lt;BR /&gt;&lt;BR /&gt;I am not sure if I understood your question correctly.&lt;BR /&gt;&lt;BR /&gt;You will need to source-in /usr/lbin/sw/contril_utils in your swpackage scripts. Along with the internal variables, there are quite a few functions available with this script that can ease your tasks. Look at the file and the documentation is in there.&lt;BR /&gt;&lt;BR /&gt;If you are talking about your own variables, then create one file that defines common variables. Dot-in the file in each of your swpackage script. This way there is only one file you need to modify to change the variables.&lt;BR /&gt;&lt;BR /&gt;-Sri&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Jun 2003 23:30:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002799#M126860</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2003-06-19T23:30:38Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall - passing variables to control scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002800#M126861</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If the number of variables are less, you can even try with ENVIRONMENT VARIABLEs. You can use that variable in your script and in the term you start swinstall, don't forget to set the values. Its only an blind idea. may be so perfect and I have not tried it also.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;VJ.</description>
      <pubDate>Fri, 20 Jun 2003 08:58:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002800#M126861</guid>
      <dc:creator>vasundhara</dc:creator>
      <dc:date>2003-06-20T08:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall - passing variables to control scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002801#M126862</link>
      <description>These all sound viable but what I'm looking to do is create a psf file with an additional variable with a directory and within a checkinstall script, check the existance of that directory prior to installing or re-installing.  I need to keep this with the package for the future.</description>
      <pubDate>Fri, 20 Jun 2003 11:14:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-passing-variables-to-control-scripts/m-p/3002801#M126862</guid>
      <dc:creator>Mike McDevitt</dc:creator>
      <dc:date>2003-06-20T11:14:15Z</dc:date>
    </item>
  </channel>
</rss>

