On Tue, 2004-01-20 at 19:36, Daniel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> > Sure we can do something like this, but what shall our trigger be?
> >
> 
> I think the existance of the file is a trigger enough
> 
> > How about something like this?
> >
> > if [ `use this_trigger` ] ; then
> > 	for conf in {${PN}-${PV}-${PR},${PN}-${PV},${PN}}.config
> > 		if [ -r /etc/${PN}/${conf} ] ; then
> > 			cp ${conf} ${S}/.config
> > 			break;
> > 		fi
> > 	done
> > fi
> >
> > [ ! -r .config ] && make a config
> > .. existing stuff
> >
> > post install phase
> >
> > [ `use this_trigger` ] && copy .confg /etc/${PN}/${PN}.config
> 



> This could just be default (no trigger) - I think lisa has done it a few times 
> in her ebuilds.
> 

I'd rather have a trigger here. The reason for that is I'd prefer to
allow the ebuild to continue to attempt to set all the latest settings
dynamically and having a missing option in a .config could/might cause
some interactivity out of the build process which I want to avoid.

This might be a little extreme but do you think we should slap an extra
ARCH || CHOST|| CCHOST directory into the ${ROOT}/etc/busybox/whatever/
to allow for unique cross compiling busybox configs?


> >
> > -----
> >
> > Idea here would be fine grained config control by searching
> > /etc/busybox/ for
> >
> > [package]-[version]-[revision].config
> > [package]-[version].config
> > [package].config
> >
> 
> I realy like this idea.
> 
> I like how the default is ${PN}.config too.
> 
> > The config would be searched for in that order and once a config is copied,
> > no more attempts would be made.
> 
> Very good.
> 
> Daniel
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFADcmmTDSbtjKmTcgRAmwrAKClw7bHtW8BO/qeriIvXSrci9z9KACfQkJq
> q85z8ms6dXKAqTi/ualNsWM=
> =rYlX
> -----END PGP SIGNATURE-----
> 
> 
> --
> gentoo-embedded@g.o mailing list
-- 
Ned Ludd <solar@g.o>
Gentoo Linux Developer