Bug 32546 - Remove fully-qualified lib symlinks from devel/jakarta-ant
Summary: Remove fully-qualified lib symlinks from devel/jakarta-ant
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Ernst de Haan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-06 03:40 UTC by chrise
Modified: 2002-05-08 08:19 UTC (History)
0 users

See Also:


Attachments
file.diff (804 bytes, patch)
2001-12-06 03:40 UTC, chrise
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description chrise 2001-12-06 03:40:01 UTC
devel/jakarta-ant installs fully-qualified symlinks in ${PORTDESTDIR}/lib,
which makes exporting ${LOCALBASE}/share/java problematic.

For example, I export /usr/local/share/java and mount it on a number of
different platforms (e.g., FreeBSD, Linux, OSX). It doesn't really make sense
to export /usr/local (or even /usr/local/share) to these clients; so I simply
mount server:/usr/local/share/java as /java. However, devel/jakarta-ant
creates two fully-qualified links, which in the above example point to
/usr/local/share/java/classes/jaxp.jar (and ...crimson.jar). If that mountpoint
doesn't exist on the client, ant execution fails.

How-To-Repeat: Export /usr/local/share/java and mount it on a client as /java. Execute
/java/jakarta-ant-1.4.1/bin/ant.
Comment 1 Patrick Li freebsd_committer freebsd_triage 2001-12-06 04:04:22 UTC
Responsible Changed
From-To: freebsd-ports->znerd

Over to maintainer
Comment 2 Ernst de Haan freebsd_committer freebsd_triage 2002-05-07 13:10:56 UTC
State Changed
From-To: open->patched

Fixed this in jakart-ant-1.4.1_2. Please confirm that 
it is okay now.
Comment 3 chrise 2002-05-08 05:48:12 UTC
On Tue, May 07, 2002 at 05:11:39AM -0700, znerd@FreeBSD.org wrote:
> Synopsis: Remove fully-qualified lib symlinks from devel/jakarta-ant
> 
> Fixed this in jakart-ant-1.4.1_2. Please confirm that
> it is okay now.

It is okay now.

-- 
Christopher Elkins
Comment 4 Ernst de Haan freebsd_committer freebsd_triage 2002-05-08 08:18:39 UTC
State Changed
From-To: patched->closed

Originator confirmed that the problem is fixed.