Hi, Scott Schaefer <saschae...@neurodiverse.org> writes: > From reading your report and your patch, I believe you can achieve > this with the "custom scripting" interface > (/usr/share/doc/piuparts/README.html or > http://piuparts.debian.org/doc/README.html#_custom_scripts_with_piuparts). > While perhaps not ideal, this interface provides a 'modular way to add > new tests'.
Looks good indeed but is this only for my private tests? How do I get my tests to run on piuparts.debian.org? > In order to verify I am understanding ... > > You seemingly need a way to determine if <pattern> is anywhere in the > "list of" Depends:; thus, your patch causes this to be built even in > absence of --warn-on-others. You then want to be able to test > (ideally, via regexp ?) for presence of >=1 patterns in this set, and > conditionally run your additional test(s) based on presence/absence of > these patterns. For example yes. The debian policy says that such a depends needs to exist in a package that ships emacs addon packages that do byte-compilation. > While I have not attempted to produce set of shell scripts that > provides this functionality, I believe there is no fundamental > constraint in the interface that would preclude doing so. Am I > misunderstanding; i.e. is there some way the current interface does > fails to address your needs ? I didn't notice this custom scripting interface at all at that time. > Finally, note your patch appears to unconditionally install and purge > emacs if you run the test; this is likely not correct, since emacs may > have either already been installed (dist-upgrade), or been installed > by install_packages, so that this may then lead to subsequent error(s) > during purge. True. -Timo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
