168631 – sys-apps/sed ebuild doesn't create /usr/bin/sed symlink

Bug 168631 - sys-apps/sed ebuild doesn't create /usr/bin/sed symlink

Summary: sys-apps/sed ebuild doesn't create /usr/bin/sed symlink

Status:	RESOLVED DUPLICATE of bug 122260

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-02-27 20:28 UTC by Davide Cendron (RETIRED)
Modified:	2007-02-27 20:42 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

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 Davide Cendron (RETIRED) gentoo-dev

2007-02-27 20:28:07 UTC

By default sys-apps/sed installs the binary in /bin, but a lot of programs search it in /usr/bin (es. eselect, run "grep sed /usr/share/eselect//libs/core.bash" to see this).

In fact,"equery b /usr/bin/sed" and "qfile /usr/bin/sed" don't return any matching package, so this symlink doesn't belong to any package.

I think that is a "forced" symlink, inclueded in stage3.

If my suppositions are true, i suggest to add a /usr/bin/sed symlink creation on ebuilds.

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2007-02-27 20:42:48 UTC


*** This bug has been marked as a duplicate of bug 122260 ***