Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
Hallo Hubert,
* Hubert Schmid wrote:
>I don't insist on this name. Are there any further packages in Debian
>(except kernel-package) that build Debian packages? If someone has a good
>name for the package and/or the executable shell script, then I will
>rename the package.
I don't know of any more, but I have a mpkg-opera waiting to be more
usefull :) I find the 'mpkg-' quite nice wrt indicating a installer
script which results in a package.
>Between, I added support for Blackdown J2RE/SDK 1.3 and 1.4 and fixed a
>problem with woody (du --apparent-size).
I would like to send a patch for IBM1.4 but I haven't heard from you
since my last mail.
I really would like to get the new policy added to your script, but I
fear that there are some problems with the auxilary packages:
The java-config file would go into the aux package and so any
package, which want to use a JVM via findjava needs to depend on
either the chain 'package->packagedebian' or directly on
'packagedebian'.
The second is IMO ugly (everytime the suffix...) and the first would
require, that package depends on packagedebian, which would mean that
the package is basicly uninstalable: packagedebian will be installed
via apt, and the package itself only via 'sudo dpkg -i'. In both
situation it would mean, that the dependecies of each package are not
satisfied. Both Depends: on each other, but the current package manager
which wants to install the package does not know about the other.
IMO it would be nice, if that could be solved first, otherwiese we
need lots of 'Conflicts:' lines just for backward compatibility. My
idea was it to rename the 'upstream package' to "package-upstream" and
'packagedebian' to "package". That way, it looks clean if a app
depends on sun-jdk-1.4 and the dependency chain is ok: first install
the upstream package via dpkg and then the debian glue via apt.
My 0.02€
Jan
--
Reply to: