Date: Sun, 26 Oct 2003 18:00:25 +0100 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-java@freebsd.org Subject: Re: Javadocs and pkg-plist Message-ID: <3F9BFDA9.6040907@fillmore-labs.com> In-Reply-To: <20031026153931.GA4603@happy-idiot-talk.infracaninophile.co.uk> References: <20031026153931.GA4603@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman wrote: > Dear ports, > > Greg Lewis pointed out to me a problem with a new port I had submitted > (ports/57753), and on investigation it turns out that the same thing > may affect several ports in the tree. > > The affected ports will be those that install api documentation which > they generate by running javadoc(1) themselves, and that can be > installed using one of several different JDK versions, and that don't > build their pkg-plist dynamically. > > It turns out that javadoc from Java 1.4.x will generate two extra > files compared to javadoc from Java 1.3.x: 'allclasses-noframe.html' > and 'constant-values.html'. These may or may not be listed in the > pkg-plist for the port, depending on which version the maintainer > happened to be using at the time. I haven't been able to test any > earlier Java versions for similar problems. How about using a dynamic packing list, like the INFO macro? I posted a proposal to PR 57778: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/57778 I think it's difficult to keep a static list of dynamically generated documentation up to date.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F9BFDA9.6040907>