Title: RE: [Oscar-devel] Question regarding Oscar Packaging
Yes, there is no need to have a script, this should all be handled via the built-in functions of RPM.
 
Cheers,
 
Bernard


From: Kshitij Shashank Limaye [mailto:[EMAIL PROTECTED]
Sent: Fri 12/08/2005 00:57
To: Bernard Li
Cc: [email protected]
Subject: RE: [Oscar-devel] Question regarding Oscar Packaging

Hello bernard,
The script is part of the rpm itself right now. Its in the /opt/globus folder.
this is how the rpm spec looks like.

Summary: A Globus Toolkit version 3.2 installer
Name: globus-oscar
Version: 3.2
Release: 1
Copyright: GPL
Group: Application
Source:
http://www.globus.org/toolkit/downloads/3.2.0/gt3.2-all-source-installer.tar.gz
BuildRoot: /usr/test/globus

%description
An automated Globus Toolkit ver 3.2 Installer

%post
python /opt/globus/globus_configure.py
%files
/opt/globus/gt3.2-all-source-installer.tar.gz
/opt/globus/globus_configure.py
/opt/globus/gate
/opt/globus/ftp

Are you suggesting to untar the tar ball in %prep section and do whatever work
the rest of script did, in the %post section. i.e eleminate calling any
script.

I just ran the script from the prompt and it works fine. When run
through rpm ,
it seems to be giving problems for the commands ./install_gt3 ../gt3.2 &
./install_mmjfs ../gt3.2.

I will look into the .spec files from the Oscar repository as you suggested.

Regards,
Kshitij

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply via email to