Date: Mon, 23 Jun 2008 13:33:13 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Issues with portmaster Message-ID: <20080623133313.4d45819b@gumby.homeunix.com.> In-Reply-To: <485F6585.2040307@FreeBSD.org> References: <20080622020728.GC13734@server.vk2pj.dyndns.org> <485DF018.5020703@FreeBSD.org> <485F4B7E.3040905@FreeBSD.org> <485F4EE1.9040603@FreeBSD.org> <485F5582.5040101@FreeBSD.org> <20080623084308.GA51236@wep4017.physik.uni-wuerzburg.de> <485F6585.2040307@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Jun 2008 10:57:41 +0200 Alex Dupre <ale@FreeBSD.org> wrote: > Alexey Shuvaev ha scritto: > > It seems I don't understand something here. Can someone explain why > > jdk ports need to set BUILD_DEPENDS on diablo-jdk15 unconditionally? > > (nearly) every JDK port needs an already usable/installed JDK to > bootstrap the compilation. This is the reason of the BUILD_DEPENDS on > javac that you cannot remove. But the port providing the javac binary > could not be the diablo-jdk. The thing is that, IIRC, it doesn't have to create a dependency at all, unless the functionality is missing. It's not simply a case of it creating a normally dependency in the sense of: install this port if that file is not found. The makefile has logic to detect which java ports are installed, so it doesn't build a second bootstap port, but it doesn't carry it through to removing the dependency once bootstrapping is no longer required. I reported this problem a long time ago after I spotted that portmanager was reinstalling a linux java version. I thought the maintainer was going to fix it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080623133313.4d45819b>