From: Kshitij Limaye [mailto:[EMAIL PROTECTED]
Sent: Thu 04/08/2005 19:26
To: Bernard Li
Cc: [email protected]
Subject: Re: [Oscar-devel] Question regarding Oscar Packaging
Hello Bernard,
Thanks a lot for replying and letting me know
about java/ant problem
solution.I am guessing that there would be a strong
possibility that the
user has Java already (as its too common) and we
installing java and
setting environmental variables like JAVA_HOME might
disrupt his
settings? So can we dynamically decide which rpms to install
using the
scripts recognised by OSCAR?
About /opt/globus, earlier
I had created the exact directory structure
as you suggested, maybe I
had confused myself over how it would work. I
included both the .tar.gz and
the python script in the /opt/globus while
making the rpm and it does the
rest.
I am attaching the config.xml as an attachement.
I am going create a
package with java and apache-ant in it and remove
the configurator for the
time being as you suggested.
Thanks in
advance,
Regards,
Kshitij
Bernard Li wrote:
> Hi
Kshitij:
>
> It might be better if we just bundle java and
apache-ant with the
> package and install them all the time (in /opt) - in
this case we have
> more control over supported versions for these
third-party
> applications. I guess we do need to find out whether
it is okay for
> us to distribute java (and apache-ant) in RPM
format.
>
> What files will go in /opt/globus? If there
are multiple files and/or
> programs, perhaps you can wrap it into a RPM,
something like
> 'globus-oscar-1.0.rpm' and after you install it, it will
create
> /opt/globus as well as all the other necessary programs - how
does
> that sound?
>
> BTW, I was only able to view the
post_configure.txt file, none of the
> other files came
through.
>
> Cheers,
>
>
Bernard
>
>
------------------------------------------------------------------------
>
*From:* [EMAIL PROTECTED] on behalf of Kshitij
>
Shashank Limaye
> *Sent:* Wed 03/08/2005 09:10
> *To:*
[email protected]
> *Subject:* [Oscar-devel] Question
regarding Oscar Packaging
>
> Hello,
> I am trying to create a
Globus-Oscar Package. I had a few questions
> regarding
> the
packaging,as I have reached midway of the package creation.
> Here is what
I did.
>
> 1. I created rpms for junit, apache-ant (pre-requisites
for Globus)
> and Globus
> with installtion directory as /opt (Oscar
default).
>
> 2. Created a package area as suggested by Howto and
put rpms in RPMS area.
>
> 3. Wrote a config.xml (attached for
viewing)
>
> 4. Wrote a configurator.html for configuartion as
suggested. The
> reason for
> writing the configurator is that
Globus installtion cannot proceed
> without Java
> being installed
and JAVA_HOME being set. Also I want the check with
> user if
>
Apache-ant has been installed or not. If not then we install it.
>
>
5. I wrote the post_configure as suggested. So the documentation says
>
that a
> globus.conf file will be generated. Now I want to read this conf
file
> which
> would have a user "yes", "no" (on whether JAVA or ANT
is installed) for
> questions and then decide which rpm to
install.
>
> 6. I couldnt locate in the document the next step to be
done to read
> the conf
> file and decide on the rpm to install. Or
do the rpms have to be
> intelligent
> enough to read the .conf
file. As the next script after post_configure is
>
post_server_rpm_install, which is post rpm installtion, I need to
> decide
based
> on results of post_configure whether or not to install
apache-ant.
> Also if java
> hasnt been installed then I should not
proceed with rpm installtions.
>
> 7. Also I need the setup script
to generate a folder /opt/globus for
> me. Is that
> possible ( I
mean conferring to the Oscar standards).
>
>
> I hope I have
explained my problem. Please let me know how I can
> proceed with
>
the packaging.
> I have attached the config.xml, configurator.html and
post_configure
> script for
> your viewing.
>
> Thanks
in advance.
> Regards,
> Kshitij
Limaye
>
>
>
>
----------------------------------------------------------------
> This
message was sent using IMP, the Internet Messaging
Program.
>
