On Thu, 27 Dec 2007 21:28:41 +0100 Michael Haubenwallner <[EMAIL PROTECTED]> wrote: > This also could be done as (using 'ebuild' instead of 'emerge') > > #! /usr/bin/env ebuild.1 > > and PM could provide some 'ebuild.1' executable, at the bare mimimum > doing nothing but > > #! /bin/sh > exec ebuild --eapi 1 "$@"
But *why*? We've finally almost gotten people away from installing things using ebuild. Why on earth would we want to bring it back? The correct way to install a package is through the nice, friendly, mask checking, dependency resolving package manager frontend. There is no correct action that can be taken when an ebuild is executed on its own, so ebuilds shouldn't be executable on their own. -- Ciaran McCreesh
signature.asc
Description: PGP signature
