Bug 87398 - WITH_OGG vs. WITH_LIBOGG in some ports
Summary: WITH_OGG vs. WITH_LIBOGG in some ports
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: Michael Johnson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-13 19:40 UTC by Zahemszky@, Gábor
Modified: 2005-11-05 07:28 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zahemszky@, Gábor 2005-10-13 19:40:18 UTC 
There are so many ports in FreeBSD, that has libogg dependency (transcode,
vlc, mplayer, etc). But at least one of them, audio/lopster use an incorrect
name - all of them use the WITH(OUT)?_OGG, but lopster uses the (I think)
incorrect WITH(OUT)?_LIBOGG  make variable.

Fix: 

In audio/lopster/Makefile, change the WITH_LIBOGG (and WITHOUT_LIBOGG)
references to WITH_OGG (and WITHOUT_OGG).
How-To-Repeat: 	egrep -R 'WITH(OUT)?_(LIB)?OGG' /usr/ports
Comment 1 Michael Johnson freebsd_committer freebsd_triage 2005-10-15 02:51:34 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ahze

Handle also since I'm the only committer of these ports.
Comment 2 edwin 2005-10-15 03:00:27 UTC 
On Sat, Oct 15, 2005 at 01:51:51AM +0000, Michael Johnson wrote:
> Synopsis: WITH_OGG vs. WITH_LIBOGG in some ports
> 
> Responsible-Changed-From-To: freebsd-ports-bugs->ahze 
> Responsible-Changed-By: ahze
> Responsible-Changed-When: Sat Oct 15 01:51:34 GMT 2005
> Responsible-Changed-Why: 
> Handle also since I'm the only committer of these ports.

I forgot to close this PR yesterday.

Edwin
-- 
Edwin Groothuis      |            Personal website: http://www.mavetju.org
edwin@mavetju.org    |          Weblog: http://weblog.barnet.com.au/edwin/
Comment 3 Michael Johnson freebsd_committer freebsd_triage 2005-10-15 05:30:04 UTC 
State Changed
From-To: open->analyzed

Work is being done to work out this problem.
Comment 4 Michael Johnson freebsd_committer freebsd_triage 2005-11-05 07:27:45 UTC 
State Changed
From-To: analyzed->closed

- Close this pr, see ports/87374 for more details