On Friday 10 February 2006 01:01, Ciaran McCreesh wrote:
> Version 1.0 of eselect, the modular configuration framework, is now
> out. All changes since 1.0_rc2 have been bugfixes.
>
> We haven't split out some of the "shipped with eselect but not core
> functionality" modules in this release, since I didn't want to break
> anything horribly -- that will probably be done for 1.1. However, we're
> providing a stable API now, so the "keep modules somewhere where the
> eselect people can find them and fix them for you" request is lifted.
>
> And since so few people seem to know this, despite it being a design
> feature that goes back to the very first random prototype hack: you
> don't have to run eselect module-name <args>. Many modules install a
> module-name-config or an update-module-name or somesuch symlink, and
> this is automatically recognised and converted internally.
>
> [ No, I'm not the guy in charge of eselect. That's Aaron, but he's busy
> and I needed eselect-1.0 before I could get GLEP 42 finalised. You
> can look forward to eselect 1.0.1 when he returns and finds all the
> stuff that I forgot to fix. ]

Is this a quirk or intentional:

# eselect kernel show
Current kernel symlink:
  linux-2.6.14.3/

(notice the trailing slash there)

I've attached a quick and silly hack to clean it up.

-- 
Eldad Zack <[EMAIL PROTECTED]>
Key/Fingerprint at pgp.mit.edu, ID 0x96EA0A93
--- kernel.eselect.orig	2006-02-12 01:30:54.000000000 +0200
+++ kernel.eselect	2006-02-12 01:36:03.000000000 +0200
@@ -46,7 +46,7 @@
 do_show() {
 	write_list_start "Current kernel symlink:"
 	if [[ -L "${ROOT}/usr/src/linux" ]] ; then
-		write_kv_list_entry "$(readlink ${ROOT}/usr/src/linux )" ""
+		write_kv_list_entry "$(dirname $(readlink ${ROOT}/usr/src/linux ) )" ""
 	else
 		write_kv_list_entry "(unset)" ""
 	fi

Attachment: pgpebixAEphw7.pgp
Description: PGP signature

Reply via email to