Jason and myself had talked about briefly but not in any depth about
post sync actions. Quickly after the basic idea was accepted it
started to become clear that a set of default triggered may be
desired.
So I was thinking like if portage installed something like the
following or if we changed the behavior now in emerge.py before the
existing become to widely adopted to do more or less the same thing
that this bash script does.
#!/bin/sh
# Copyright 2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
if [ -d /etc/portage/postsync.d/ ]; then
for f in /etc/portage/postsync.d/* ; do
if [ -x ${f} ] ; then
${f}
fi
done
else
:
fi
##############################
How do you think we should handle it?
Should we install a post_sync in a postinst phase outside of portage's
handling if and only if not post_sync already exists?
Should we change it to handled a postsync.d by default?
Should we do both? I'm open as heck but would like to start to
finalize then document it's behavior. I feel it could be one of the
next untapped really useful features of portage. glsa-checking, news
handling, search db updating, and stuff etc..
--
Ned Ludd <[EMAIL PROTECTED]>
Gentoo Linux
--
[email protected] mailing list
