252828 – app-admin/eselect-boost: does not select a boost version by default

Bug 252828 - app-admin/eselect-boost: does not select a boost version by default

Summary: app-admin/eselect-boost: does not select a boost version by default

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High normal (vote)
Assignee:	Tiziano Müller (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2008-12-28 16:23 UTC by Santiago M. Mola (RETIRED)
Modified:	2009-01-06 12:05 UTC (History)
CC List:	2 users (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 Santiago M. Mola (RETIRED) gentoo-dev

2008-12-28 16:23:23 UTC

I've just installed dev-libs/boost-1.35.0-r3 and dev-libs/boost-1.36.0.

# eselect boost list
Available boost versions:
  [1]   boost-1_35
  [2]   boost-1_36

# eselect boost show
Current boost version:
  (unset)

# eselect boost update
!!! Error: Couldn't remove existing installation
Terminado (killed)

Maybe boost should set a version when none is set yet, and 'update' should not fail when none is set.

Comment 1 Roel Brook 2009-01-04 02:08:45 UTC

It might also be worth it to call eselect after merging a boost version.

i.e. after installing boost 1.37 (which is currently masked), portage will un-emerge the current version of boost (in my case 1.35), which left the /usr/include/boost symlink pointing nowhere.

Comment 2 Tiziano Müller (RETIRED) gentoo-dev

2009-01-06 12:05:52 UTC

Bug solved in version 0.2.
No, portage will/should not automatically un-merge 1.35 since they're in different slots. That's the reason why we need boost-eselect after all.