Mailinglist Archive: opensuse-packaging (139 mails)

[Adrian Schröter <adrian@xxxxxxx>]

On Sunday 02 March 2008 00:08:45 wrote Pascal Bleser:
> Adrian Schröter wrote:
> > On Thursday 28 February 2008 16:49:10 wrote Michal Vyskocil:
>
> [...]
>
> > That should not be needed, we can map java-devel to the correct java
> > version in the distribution configurations.
>
> ...which only works in the OBS.

The selection of a specific one, yes. But java-devel is provided by the java 
package.

> > Acctually, you should not BuildRequire a certain java version at all, as
> > long you do not want to enforce the exclusive use with this version.
>
> Right, the typical requirement is "I want Sun JDK version >= x.x.x" ;)
> (at least on ix86 and x86_64).

But this should be done only, if it is sure that this is the single java 
version which does work. In general all java version should work for almost 
all java packages. Therefore it is better to use java-devel .

> > Better use java-devel everywhere and tell us, which java version by
> > default should be selected dependening on the architecture.
>
> But that has to be provided by the packages themselves, not (only) by
> OBS tricks.

A java package should in general work with all java versions, otherwise we can 
never upgrade a java or switch to some other java. This is esp. important 
when it comes to other architectures, Sun Java does not exist for all. So an 
explicit requirement to Sun java would mean that your java package needs to 
get disabled on these architectures.


-- 

Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx

---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx