440430 – app-shells/gentoo-bashcomp-20101217-r1: some elog messages should only be shown for the first install.

Bug 440430 - app-shells/gentoo-bashcomp-20101217-r1: some elog messages should only be shown for the first install.

Summary: app-shells/gentoo-bashcomp-20101217-r1: some elog messages should only be sho...

Status:	RESOLVED OBSOLETE

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Gentoo Shell Tools project

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	first-time-messages
	Show dependency tree

Reported:	2012-10-31 10:58 UTC by poletti.marco
Modified:	2018-11-09 08:31 UTC (History)
CC List:	1 user (show)

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 poletti.marco 2012-10-31 10:58:40 UTC

Disclaimer: this bug has been filed in a semi-automated manner.

When emerging the package app-shells/gentoo-bashcomp-20101217-r1, the following elog messages are displayed:

 * To enable command-line completion for gentoo-bashcomp, run:
 * 
 *   eselect bashcomp enable gentoo
 * 
 * to install locally, or
 * 
 *   eselect bashcomp enable --global gentoo
 * 
 * to install system-wide. (and/or repoman instead of gentoo if you use
 * repoman frequently)

Such messages should only be displayed when the package is a new install.
These situations can be checked in the ebuild as follows:

if ! has_version 'app-shells/gentoo-bashcomp'; then

See the tracker bug 440214 for more details.

Comment 1 Pacho Ramos gentoo-dev

2013-02-07 19:52:02 UTC

It should behave like new bash-completion-r1.eclass and not show any message like this (also, would be interesting if ebuild could state why this cannot use such eclass ;))

Comment 2 Pacho Ramos gentoo-dev

2018-11-09 08:31:16 UTC

now relies on eclass for that