config.py moved?

[Stefan Reinauer]

* ron minnich <rminnich at lanl.gov> [031013 17:07]:
> > config.py moved to the target directory. Did this happen on purpose?
> > Should it not move to config/solo/solo instead of config/solo if it
> > moves at all?
> 
> config.py shouldn't even be in cvs. It is derived from config.g. 

Yes, that's why util/newconfig has the following entries in it's
.cvsignore:
config.py
yappsrt.pyc
parsedesc.py

> I think you are right, however, for a given target there probably ought to 
> be a config.py for that target, since not all targets are built on the 
> same box. 

This is probably a henn-egg-problem - the target directory is created
by config.py, isn't it?

Best regards,
  Stefan Reinauer
  
-- 
Architecture Team
    SuSE Linux AG