Date: Tue, 4 Mar 2008 10:09:57 -0800 (PST) From: pjd <peter_dunning@dsl.pipex.com> To: freebsd-ports@freebsd.org Subject: Re: interactive ports - the plague Message-ID: <15833478.post@talk.nabble.com> In-Reply-To: <200803031205.07906.beech@freebsd.org> References: <47CBC3C5.9050007@bsdforen.de> <20080303155354.2043d131@gumby.homeunix.com.> <47CC26F3.7020709@cyberbotx.com> <15808613.post@talk.nabble.com> <20080303195704.GA18100@soaustin.net> <200803031201.54445.beech@freebsd.org> <200803031205.07906.beech@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Beech Rintoul-5 wrote: > > >> > > With me the JDK ports stop and demand I manually download the >> > > files, which is even more irritating >> > >> > Given Sun's licensing requirements, what is your suggestion? > > Sorry, having that port just fail seems to be the right thing to do. > FWIW, it doesn't hang up portupgrade. > > Well does it help when you are attempting openoffice.org and the failure of the jdk ports leads to the entire build of the final package itself being called off, thus effectively canceling the night's build anyway. Personally I would like to see all licenses and configuration options resolved at the start of portupgrade (so they are all done in one go) and then followed by the compilation and downloads, that way nothing gets canceled or stalled unless there is a genuine problem -- View this message in context: http://www.nabble.com/interactive-ports---the-plague-tp15800371p15833478.html Sent from the freebsd-ports mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15833478.post>