Bug#688319: devscripts: Please consider including the 'yodack' tool

[Benjamin Drung]

Am Sonntag, den 07.10.2012, 13:19 +0200 schrieb Gergely Nagy:
> Benjamin Drung <bdrung at debian.org> writes:
> 
> > Am Freitag, den 28.09.2012, 15:07 +0200 schrieb Gergely Nagy:
> >> Let me know if there's anything I can do to help this script be
> >> integrated into devscripts!
> >
> > This is just my opinion: I like to see shunit2 tests for yodack before
> > integrating it into devscripts. To make yodack testable, it should be
> > possible to output the command files instead of uploading them. Then you
> > can compare the command files with the expected content. You can also
> > test the return value of yodack and test the behavior for invalid input.
> 
> There's a reasonably complete test suite in yodack's git now. It does
> not test the verification dialog yet, I have to think of a sane way to
> do that, but pretty much everything else should be covered, I think.

Thanks. I think it's time to move the script to devscripts. Can you
create a git formatted patch against our jessie branch that adds the
script to our package? The source package layout of your yodack branch
is a little different than the current devscripts layout.

-- 
Benjamin Drung
Debian & Ubuntu Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20121011/683437b8/attachment.pgp>