Hi, usetest is a tester for ebuild file in all USE flag patterns. For example, if ebuildfile has IUSE="cjk nls" variables, usetest lets run following commands: USE=" cjk nls" emerge =ebuildname-version USE="-cjk nls" emerge =ebuildname-version USE=" cjk -nls" emerge =ebuildname-version USE="-cjk -nls" emerge =ebuildname-version Thus, usetest can test ebuild automatically. Thank you,
Created attachment 22594 [details] usetest-0.1.ebuild
something for the new gentoolkit-dev
Seems that the URL is dead
URL has moved. also SRC_URI has moved too, so I attach a diff for ebuild.
Created attachment 41253 [details, diff] diff for URL change
homepage is living. not CANTFIX... :(
Ok, I see a few problems with it: - no copyright information (GPL, public domain, ...) - depends on ruby, shouldn't be a big problem to rewrite that part in python - 'grep IUSE ${EBUILD}' will miss flags if eclasses modify IUSE or IUSE spans more than one line The idea is good but the implementation needs to be improved.
I see. I intend to distribute this under the GPL-2, I'll also specify it in source code. I'll post again after fix those problems and rewrite in Python or Bash. Thank you for your comments.
Rewritten in Python with my friend together. This version has two type. one is calling emerge using os.system. Its character is: * can test completely. * may be break test environment because it does `merge' also (but may be able to avoid using --buildpkgonly and --oneshot). Other one is calling portage.doebuild. Its character is: * cannot control output from doebuild, from this script. * cannot test `postinst' and etc. because it does only `clean', `setup', `unpack', `compile' and `install' (for the meantime). * can keep test environment. which is better?
Created attachment 41606 [details] `calls emerge' type
Created attachment 41607 [details] `calls doebuild' type
Well, packages won't get picked up by portage or the package if they aren't merged so just installing the potential deps into $D isn't enough. This should be used in a chroot anyway, so merging isn't really a big issue. I'll check it in more detail later.
See app-portage/gatt-svn. If you have suggestions wrt gatt, file a bug for the maintainer. Closing this bug as it's dead, thanks.