On Tue, 2004-01-20 at 18:45, Daniel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wed, 21 Jan 2004 09:05 am, david@... wrote:
> > I noticed that the default busybox Config.h(the file that selects what
> > applets to compile) doesn't include a few things most systems will prolly
> > need(freeramdisk for example).
> >
> > is there an easy way we can provide people with the capability to
> > construct their own customized Config.h and have emerge build busybox
> > with that file ?  USE flags are a bit unrealistic in this case.
> > like... 'place your own/modify the config in
> > .../busybox/files/Config.h'
> >
> 
> Could, as I'm attempt to do (I copied off someone else)
> 1. first emerge places the config file in /etc/embedded/busybox.config
> 2. user can edit the file
> 3. next emerge uses /etc/mebedded/busybox.config as a config.


Sure we can do something like this, but what shall our trigger be?

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

-----

Idea here would be fine grained config control by searching
/etc/busybox/ for

[package]-[version]-[revision].config
[package]-[version].config
[package].config 

The config would be searched for in that order and once a config is copied, 
no more attempts would be made.

> 
> Daniel
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFADb2NTDSbtjKmTcgRAp3tAKChFWoGTvDqGnf2mRaJmWhT3EpszQCggGLh
> LI0OtAYyIvehnVx5eb8096I=
> =MEIj
> -----END PGP SIGNATURE-----
> 
> 
> --
> gentoo-embedded@g.o mailing list
-- 
Ned Ludd <solar@g.o>
Gentoo Linux Developer