>
> I will write a mini setup program as Microsft does ;)
>
> Up to now I just "echo" out the instructions and the license (with a
> line that sounds like 'using the software presumes you have accepted the
> license terms at all"
Intel's free compiler, Mathematica, and maple take the followi
Rick Thomas wrote:
>When the script is run by rpm, it probably has input redirected from
>/dev/null. As the docs say, it should be non-interactive. Anything else
>will break scripted installations.
>
>
>
>
Yes. It is so.
In fact I used something like
%pre
$bashscript = /tmp/myfile
echo "#!
Stew Benedict wrote:
>Are you saying the script behave differently in the RPM than if you just
>run it? I would do something a little more bulletproof, which would force
>them to answer one of your choices, unless they ctrl-C out of it:
>
>
>
>
Yes (I am saying the script behave differently).
On Fri, 31 May 2002, Miguel Beccari wrote:
> I builded a RPM from scratch of an application of mine.
>
> The SRC rpm works: it builds 2 i586 architecture packages, it has got
> good controls, it check dependecies and so on.
>
> My trouble is this: how to force the user to answer some question
Miguel Beccari wrote:
>
>
> %pre
>
> echo "Bla bla bla.";
> echo -n "Answer (yes | no | later)";
> read chiave
> while ( test -z $chiave ); do
>read chiave
> done;
>
OK. In the docs I read:
There are certain caveats about these scripts which you should take into
account. Number on
