From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2307 invoked by uid 1002); 8 Dec 2003 04:14:32 -0600 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 19021 invoked from network); 8 Dec 2003 04:14:31 -0600 From: "Yannick Le Saint (kyncani)" Reply-To: y.lesaint@free.fr To: gentoo-portage-dev@gentoo.org Content-Type: text/plain Message-Id: <1070878448.4786.33.camel@kyncani.lesaint> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 08 Dec 2003 10:14:11 +0000 Content-Transfer-Encoding: 7bit Subject: [gentoo-portage-dev] Local post_install script X-Archives-Salt: cf8e32a0-51d5-469d-975d-605d57546782 X-Archives-Hash: 85154b39641b4d57b44578f8b36a568b What about having local post_install scripts (something like debian hooks, if i remember well) ? For example, it would be sooo cool to have a /etc/portage/portage.d/sys-kernel/vanilla-sources/post_install file of my own which would have access of every variable you can have in an ebuild. This is how my post_install script for vanilla-sources would look like : cd /usr/src || die rm -f linux &>/dev/null ln -s linux-$KV linux || die cp -f /etc/kernels/myconfig /etc/kernels/config-$KV || die nice -n 20 genkernel || die -- gentoo-portage-dev@gentoo.org mailing list