perfsonar development work

[Stijn Melis <>]

Michael Bischoff wrote:
>> Stijn Melis wrote:
>>
>>>> Tomcat can also start with GCJ. Sun JDK is not explicitly given as a
>>>> dependency, so sun JDK should be defined as a dependency for all 
>>>> perfsonar packages.
>>>>
>>>> Shame on you Michael ;)
>>>>
>>>>
>>>>
>>> So, to cut a long story short: do I have to add sun-java5-jdk or
>>> sun-java6-jdk to the dependencies? Gijs says yes, Cándido and Michael say 
>>> I don't have to
>>> change it, I'm a bit confused :)
> 
> Well that's because your at a fork in the road; You can force people to use 
> only supported
> configurations or you can allow people mix and match to better suit there 
> integration needs.
> 
> If you go for the former you save yourself from cluttering your support 
> process with issues
> related to unsupported platforms. If you go for the latter you allow more 
> flexibility to the
> end-user.
> 
> With the first in mind, you end up with the option gijs gave you. Depend on 
> sun-java
> specifically as we marked that as supported platform.
> 
> With the latter in mind you lean towards Cándido approach, allow the user 
> to choose his own
> jdk implementation but that might lead to unsupported configurations (while 
> the user might
> not be aware of it at first). We had some funny issues using the GCJ during 
> testing for
> example.
> 
> I slightly favour the first because of the following reasons:
> - you can always relax it later but the other way around might lead to a 
> lot of issues /
> disgruntled users.
> - Since we already explicitly depend on tomcat the flexibility is already 
> crippled to such
> and extend that allowing the user to choose it's jvm impl still doesn't 
> offer him much. (The
> people that use IBM impl usually use webspere as a container not tomcat.
> - bug reports would be more streamlined.
> - War distribution allows you to mix and match so it's not like we totally 
> restrict the
> option of mixing and matching configurations.
>

Okay, I will go with the first option then.

Just to conclude: for the deb files the dependencies are correct, right?

Depends: ${shlibs:Depends}, ${misc:Depends}, tomcat5.5, tomcat5.5-exist,
java5-runtime | java6-runtime | java-virtual-machine

And which package should I add for rpm? I tried jdk-1.5.0_16, but this
isn't recognized as a package.

Thanks in advance,

Stijn

>>> At the moment for deb I have the following:
>>>
>>>
>>> Depends: ${shlibs:Depends}, ${misc:Depends}, tomcat5.5, tomcat5.5-exist,
>>> java5-runtime | java6-runtime | java-virtual-machine
>>> from
>>> and for rpm I have this:
>>>
>>> # on what packages should the resulting package depend
>>> Requires: tomcat5
>>> Requires: tomcat5-exist
>>>
>>>
>>> Since the rpm part doesn't mention java I presume I have to add
>>> something there, right? And because the deb part already mentions java 
>>> runtime, I presume
>>> that one is okay, correct?
>>>
>> The problem is that the RPM's for sun java have different names for
>> different distributions. I don't remember what was decided to fix this, 
>> but leaving it out
>> isn't a big problem as long it is clear in the installation manual that 
>> sun java should be
>> installed. Please take a look at the other packages on what they do with 
>> this issue.
>>
>>
> 
> 
> Regards,
>  Michael