Bug 36109

Summary:	unifont requires package.mask'ed chkfontpath
Product:	Gentoo Linux	Reporter:	ferret <ferret-bgo>
Component:	Current packages	Assignee:	Gentoo Fonts Team <fonts>
Status:	RESOLVED FIXED
Severity:	minor	CC:	jstubbs
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description ferret 2003-12-19 04:04:13 UTC

Title says it all really... I'm just mildly baffled as to the reason for this.
Should the unifont ebuild *really* depend on chkfontpath? Should unifont be
package.mask'ed too? I have CC'ed the ebuild submitter in the hope this "bug" can
be shot down quickly and not clutter up the place. Hope that's okay.

Comment 1 Mamoru KOMACHI (RETIRED) gentoo-dev

2004-01-10 07:34:10 UTC

*** Bug 37758 has been marked as a duplicate of this bug. ***

Comment 2 Mamoru KOMACHI (RETIRED) gentoo-dev

2004-01-10 07:42:03 UTC

If we are not to unmask chkfontpath I'll remove chkfontpath from
unifont's ebuild (it isn't needed unless we want to automate
installation anyway). I knew it was marked unstable and committed
unifont but didn't notice chkfontpath was package masked (moreover, I
didn't know that foser didn't like the idea of making use of it then)

Comment 3 Donnie Berkholz (RETIRED) gentoo-dev

2004-01-18 19:21:30 UTC

Ideas here?

Comment 4 Mamoru KOMACHI (RETIRED) gentoo-dev

2004-01-19 14:55:42 UTC

Definitely it doesn't need chkfontpath, so I'll remove chkfontpath
from DEPEND and make some modification to unifont's ebuild tomorrow if
nobody is strongly against it. (In addition I'm going to mask current
chkfontpath for the sake of chkfontpath)

Comment 5 Mamoru KOMACHI (RETIRED) gentoo-dev

2004-01-21 22:59:43 UTC

I added unifont-1.0-r1, which doesn't depend on chkfontpath
and p.masked unifont-1.0 accordingly.