On Sun Aug 02 20:00, Torsten Werner wrote: > > "upstream release version". API version changes when upstream change the > > API and is encoded in the package name. > > How do I find out if the API has changed in a new upstream version?
As others have said: read the changelog, test it, look at the diffs. > You suggest some different ways to place a unversioned symlink in some > kind of *-dev package. How do you want to make sure that the same API > version is used during compile time and run time? ELF binaries solve > that problem with their static and dynamic linkers - but Java? Do we > need to always install the *-dev package even during run time? No, javahelper would convert manifest entries to the versionned jar and then dependencies to the versionned library package. The -dev would be needed at build time and just the library at runtime. If people have to use wrapper scripts which build a CLASSPATH rather than java -jar I can provide some way to replace them with the correct paths. > > Combined -dev/-doc packages > > I like that most but do not understand how does it work. Does it mean > that we need to alwayl install the *-doc package to fulfill the > runtime dependency? See above, you would just need it at build time. Matt -- Matthew Johnson
signature.asc
Description: Digital signature
