Bug 89084 - [MAINTAINER] update sysutils/portmanager
Summary: [MAINTAINER] update sysutils/portmanager
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: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-15 20:20 UTC by Michael C.Shultz
Modified: 2005-11-16 03:17 UTC (History)
1 user (show)

See Also:


Attachments
portmanager-0.3.5_1.diff (4.06 KB, patch)
2005-11-15 20:20 UTC, Michael C.Shultz
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michael C.Shultz 2005-11-15 20:20:16 UTC
	update sysutils/portmanager to ver 0.3.5_1

	1. Craig Boston <craig@yekse.gank.org> brought to my attention a problem
	with how dependency information is gathered in +CONTENT files. 

	portmanager -s (status report) uses port +CONTENT files to generate its
	report and now that is proven as not 100% accurate.  This patch modifies
	the data source for status reports from +CONTENT files to the results 
	obtained when running make -V *_DEPENDS in each port directory.

Fix: This is just a work around to the real problem
	wich resides in port infrastructure.
How-To-Repeat: 
	Install databases/p5-BerkeleyDB WITH_BDB_VER=42
	then install security/amavisd-new
	+CONTENT for amavisd-new will list the wrong 
	databases/db* for it's dependency because whatever
	generates +CONTENT files upon port registration
	is failing to consider WITH_* switches comming
	from dependent ports.
Comment 1 Marcus Alves Grando freebsd_committer freebsd_triage 2005-11-16 03:17:29 UTC
State Changed
From-To: open->closed

Committed. Thanks!