Usage of vecho in the tree

01-22-2010, 08:48 AM

A number of ebuilds use vecho from portage.

But vecho is not defined in general. It's a portage internal command.

Do we want to fix the ebuilds? Add a repoman check so we don't have to clean them regularly?
Or do we want to provide it via profiles/base/profile.bashrc like elog?

BTW: Do we want to remove the elog check from the profiles now?

./dev-scheme/bigloo/bigloo-3.2b_p2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-scheme/elk/elk-3.99.7.ebuild: vecho "Tests already run during compile"
./mail-mta/courier/courier-0.61.2.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./mail-mta/courier/courier-0.59.0.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./mail-mta/courier/courier-0.60.0.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./mail-mta/courier/courier-0.61.1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"
./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"
./dev-lang/php/php-5.2.10.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-lang/php/php-5.2.9-r2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-lang/php/php-5.2.10-r2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-lang/php/php-5.2.12.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-lang/php/php-5.2.10-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-lang/php/php-5.2.11-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-lang/php/php-5.2.11.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-lang/mono/mono-2.4.9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./dev-lang/mono/mono-1.2.5.1-r1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./dev-lang/mono/mono-1.2.6-r3.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./dev-lang/mono/mono-2.4.2.3.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./dev-lang/mono/mono-2.0.9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./dev-lang/mono/mono-9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./dev-lang/mono/mono-2.0.1-r1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
./sys-devel/clang/clang-2.6-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"

01-22-2010, 09:15 AM

* Torsten Veller <ml-en@veller.net>:
> Or do we want to provide it via profiles/base/profile.bashrc like elog?

That wouldn't work as other package managers don't source profile.bashrc.

01-27-2010, 05:58 PM

* Torsten Veller <ml-en@veller.net>:
> ./dev-scheme/bigloo/bigloo-3.2b_p2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-scheme/elk/elk-3.99.7.ebuild: vecho "Tests already run during compile"
> ./mail-mta/courier/courier-0.61.2.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./mail-mta/courier/courier-0.59.0.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./mail-mta/courier/courier-0.60.0.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./mail-mta/courier/courier-0.61.1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.10.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.9-r2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.10-r2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.12.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.10-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.11-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.11.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.4.9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-1.2.5.1-r1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-1.2.6-r3.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.4.2.3.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.0.9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.0.1-r1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./sys-devel/clang/clang-2.6-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"

I am going to change `vecho` to `echo` this weekend unless there are
objections.

--
Regards Torsten