On Tuesday, July 12, 2011 00:54:02 William Hubbs wrote: > On Mon, Jul 11, 2011 at 11:27:59PM -0400, Mike Frysinger wrote: > > i dont think we've had openrc in stable long enough to force people to > > migrate. so i'd keep the code putting along for now, and add a note to > > the feature removal schedule only after we have checks in the openrc > > ebuild that to catch upgrade paths (and perhaps even do the migration > > for users). > > We don't try at all to migrate /etc/conf.d/net; we tell the user to read > /usr/share/doc/openrc-*/net.example and do the migration themselves. Are > you suggesting automating that step? I think it would be tricky to do > that at best since there could be so many different configurations.
it would be nice to come up with some level of automated conversion. no matter how much we say "read the docs", there will always be people who do not. i think the reason the openrc upgrade has gone so smooth thus far is because how much we've done to auto-migrate settings. > Is it possible to use eerror inside the _flatten_array and _get_array > functions some how so that they will complain when they are used to > parse bash arrays? you can add an ewarn now while continuing to parse the code. but the same issue as above ... there are many systems which are headless where these will not generally be seen. -mike
signature.asc
Description: This is a digitally signed message part.
