On 2010-04-26 7:49 PM, Oliver Ripka wrote: > Hi, > > it is not a drop-in replacement, because the save, new, switch (and the > other commands supported by env) commands do not behave like the env > script. The main differences are: > > * env2 does initialize the git repository differently (no special files in > initial import to keep the history clean) > * env2 saves and restores the SVN state > * env2 symlinks files but not directories. env symlinks the files/ > directory > > It won't work as drop-in but you can certainly use it along side with env. > Migration also shouldn't be so difficult: > > env switch branch1 > env2 new branch1 > env2 save > > Note: > In the meanwhile I found bugs in the version I initially posted here on the > mailinglist and set up a git repository with a new version. You can find the > repository in the wiki entry: http://wiki.openwrt.org/inbox/env2.script Could you pick a different name for this thing? I think especially people using tab completion will be annoyed at having two completely different scripts in scripts/ with almost the same name.
- Felix _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
