Zac Medico schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ned Ludd wrote:
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 d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ned Ludd wrote:
> 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
On Thu, 2006-05-04 at 22:36 +0200, Simon Stelling wrote:
> Ned Ludd wrote:
> > #!/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
Ned Ludd wrote:
#!/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}
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
