Bugzilla Bug 42805

fontconfig (at least since ebuild 2.1-r1) have a strange dependency on ed
(>=sys-apps/ed-0.2).

ldd /usr/bin/fc-list ; ldd /usr/bin/fc-cache
does not report such depency

This binaries still works fine after unmerging sys-apps/ed

Reproducible: Always
Steps to Reproduce:
1. emerge -p fontconfig (after a stage1)

or

1. qpkg -q ed -g sys-apps (on a working system, ed is the second package)






Expected Results:  
emerge fontconfig after a stage1 should not merge ed (I prefer vi, and won't 
use ed ;).  

The last line is the one that may be incorrect 

# Copyright 1999-2003 Gentoo Technologies, Inc. 
# Distributed under the terms of the GNU General Public License v2 
# 
$Header:
/home/cvsroot/gentoo-x86/media-libs/fontconfig/fontconfig-2.1-r1.ebuild,v 
1.18 2003/11/01 09:43:54 seemant Exp $ 

inherit debug eutils 

S="${WORKDIR}/fcpackage.${PV/\./_}/fontconfig" 
DESCRIPTION="A library for configuring and customizing font access." 
HOMEPAGE="http://freedesktop.org/" 
SRC_URI="http://pdx.freedesktop.org/software/fontconfig/releases/fcpackage.
${PV/\./_}.tar.gz" 

LICENSE="fontconfig" 
SLOT="1.0" 
KEYWORDS="x86 alpha ppc sparc mips hppa arm amd64" 

# Seems like patches in freetype-2.1.2-r2 fixes bug #10028 
DEPEND=">=media-libs/freetype-2.1.2-r2 
    >=dev-libs/expat-1.95.3 
    >=sys-apps/ed-0.2"

DEPEND means it's a compile time dependency.
RDPEND means it's a run-time dependency.

So yes, you can remove ed after compiling fontconfig.

well, Theres no RDEPEND listed in fontconfig, so DEPEND="RDEPEND" in this case.

spider's right

and I guess the other point of unclarity, which both spyderous and the bug
reporter raised, is: why is ed even a DEPEND for fontconfig?

well, I'd guess that its a Makefile that uses it.  Consider also the sed
dependencies (Version specific due to how sed is called) to be moved to DEPEND
!= RDEPEND here.

unmerging ed, unmerging fontconfig, removing the ed dependency in fontconfig
ebuild and re-emerging fontconfig just works fine...

Mozilla and XFree seems to run unaffected.

i think it was some relic from earlier ebuilds & removed it from 2.2.2