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
Oliver
According to Jo-Philipp Wich on Mon, Apr 26, 2010 at 07:08:36PM +0200:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Oliver.
>
> If the env2 script is a superset of the existing evn script, are there
> any reasons to not replace that entirely?
>
> Any known incompatibilities or is it a drop-in replacement?
>
> ~ Jow
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkvVyJMACgkQdputYINPTPOk/wCcCosdbkKfrvz0e838J9HmoXB4
> XO8AoJnzvqaCTss1lKqhYuwJbj1kBziE
> =qipm
> -----END PGP SIGNATURE-----
> _______________________________________________
> openwrt-devel mailing list
> [email protected]
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
