[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#657393: RFS: skstream/0.3.6-1 [ITA] -- IOStream C++ socket Library

On 01/27/2012 07:09 PM, Jakub Wilk wrote:
> * Stephen M. Webb <stephen.webb@bregmasoft.ca>, 2012-01-27, 18:20:
>>   * debian/rules: add --with autoreconf to regenerate autoconfigury
> A typo, though I'm not sure which word you had in mind. :P

I don't see the typo.  I added "--with autoreconf" to regenerate the
autoconfigury (config.guess, config.sub, aclocal.m4, ltmain.sh,
libtools, etc).  It's all terminology I've used on other projects.  Is
there a preferred way to phrase this on Debian?

>>   * debian/control: tweaked for multi-arch
> Could you be more explicit about how it was tweaked?
> BTW, you could add "Multi-Arch: same" field to all 3 packages, so that
> there's an actual benefit from installing stuff into multi-arch
> directories. :)

I did the minimum necessary to go to debhelper compat level 9.  Do you
suggest it's better to go whole-enchilada multi-arch?  I'm not
anticipating bi-arch installs or cross-builds, but I guess it doesn't
really hurt.  I'm just less familiar with the consequences of multi-arch
so I was being conservative.

> I see test failures in my build log:

Me too. The tests rely on manually configuring the OS is a specific,
non-standard way.  Should I just disable the test targets during the
build to reduce the noise?

Stephen M. Webb  <stephen.webb@bregmasoft.ca>

Reply to: