542250 – dev-libs/beecrypt-4.2.1-r2 default useflags don't make sense

Bug 542250 - dev-libs/beecrypt-4.2.1-r2 default useflags don't make sense

Summary: dev-libs/beecrypt-4.2.1-r2 default useflags don't make sense

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	Normal trivial (vote)
Assignee:	Patrice Clement

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-03-05 11:32 UTC by Märt Bakhoff
Modified:	2015-03-06 10:35 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 Märt Bakhoff 2015-03-05 11:32:10 UTC

Installing dev-libs/beecrypt on ~amd64 with default useflags:
beecrypt-4.2.1-r2.ebuild: IUSE="java cxx python static-libs threads doc"
/usr/portage/profiles/base/make.defaults: USE="${USE} cxx"

!!! The ebuild selected to satisfy "beecrypt" has unmet requirements.
- dev-libs/beecrypt-4.2.1-r2::gentoo USE="cxx -threads ..."
The following REQUIRED_USE flag constraints are unsatisfied: cxx? ( threads )

I know I can enable the 'threads' useflag but why is this not done by default? It's really annoying that I have to edit my package.use if I just want to install it as a dependency. 

Reproducible: Always

Comment 1 Patrice Clement gentoo-dev

2015-03-06 10:25:45 UTC

I'll take care of it

Comment 2 Patrice Clement gentoo-dev

2015-03-06 10:35:11 UTC

+*beecrypt-4.2.1-r3 (06 Mar 2015)
+
+  06 Mar 2015; Patrice Clement <monsieurp@gentoo.org> +beecrypt-4.2.1-r3.ebuild,
+  beecrypt-4.2.1-r2.ebuild:
+  Turn 'threads' USE flag on by default. Fix bug 542250.
+