On Feb 22, 2011, at 5:25 PM, Gabe Black wrote: > Like I said, why can't you just do that with a simple bash alias that > appends the options to the binary? Or a wrapper script? Why make a new > tool when an existing one works just as well?
I don't think any of those mechanisms are that great. Wrapper scripts normally muck with job control, stdin, & stdout and bash aliases assume you're using a particular shell. I think aliases are just magic and will cause a lot of confusion (e.g. looking i'm just running X, never mind your shell is secretly substituting something else without telling you). If you're in the unfontunate situation of having multiple csh/bashrc files depending on what machine/cluster you're on (i do) you have to try and keep those in sync rather than just keeping all your m5 setting in sync. Finally, the last thing I want is my m5 command line to be even longer than it is now. They already wrap a couple of times on a terminal. Isn't this akin to saying, why have a .vimrc? Yes i can pass all the settings I have in my .vimrc on the command line to vim, but why would I want to? The more I think about it the more I like a configs.py or whatever you want to call it. It lets you be very simple and should provide a single place to change any environment like settings and then there won't be any random environment variables or other things grabbed in an adhoc fashion in the scripts. Regarding /dist: I think the directories of interest were binaries, disks, cpu2000. What more of a rundown do you want? Ali _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
