Bug#289245: java-package: alternatives not removed when sun-j2sdk* is removed

[Jerry Haltom]

I had played with a work of java-package that I had been working on
during the make-jpkg->java-package migration. This fork did not have
*debian packages, but just built the contents of those packages into the
generated .deb's. Worked fine. Was much cleaner.

The one caveat is that java-package itself has to install all the
*debian contents into /usr/share/java-package/ so they can be used at
runtime of java-package.

On Sat, 2005-01-08 at 03:54 +0100, Jeroen van Wolffelaar wrote:
> On Fri, Jan 07, 2005 at 04:38:11PM -0800, Steven Ihde wrote:
> > When removing a java package built by make-jpkg (e.g., "apt-get remove
> > sun-j2sdk1.4"), the alternatives installed by the package are not
> > removed.  Here's what is supposed to happen:
> > 
> (...)
> > 
> > While investigating this I noted that sun-j2sdk1.4 and
> > sun-j2sdk1.4debian each depend on the other.  This seems unnecessarily
> > complicated, and in a way is the cause of the problem:
> 
> Thank you for your elaborate analasys. Yes, I noticed that there is a
> circular dependency here, which seemed a bit odd. I decided to leave it
> alone though for 0.18, but am now reconsidering.
> 
> I can see a few reasons why those packages exist at all: a way to get
> depended on and suggested if one tries to fulfil dependencies in sarge,
> and a way users to track whether they are uptodate java-wise. The latter
> isn't being done at the moment, so I'll disregard that. Fir former
> however I can understand: Due to these *debian packages, if one needs a
> 'java2-compiler', apt will come and suggest that the *debian package can
> fulfil that depends, and in turn need a not-yet-created package.
> 
> Otoh, I see no compelling reason for the *debian packages to be depended
> on by the generated packages... those two scripts (install and remove)
> can just as well be pasted into the generated packages, much safer...
> 
> I'll need to think this over a bit more, meanwhile, any input welcome on
> what do with this. Just dropping all *debian packages from java-package
> sounds tempting, but otoh, I'm not sure whether it's a good idea.
> 
> --Jeroen
> 
-- 
Jerry Haltom <wasabi@larvalstage.net>