Ben Gertzfield wrote:
> So I was thinking it'd be nice to warn developers of shared library
> packages that they should have the -dev file depend with a versioned
> depends on the real lib file.
Either that or make the .so link point to the soname link, instead of
to the actual library. Then the
> "Adam" == Adam Di Carlo <[EMAIL PROTECTED]> writes:
Adam> Well, rather than making an exemption, the point is pretty
Adam> simple:
Adam> If a package depends on a specific version of a -dev or
Adam> lib* pacakge, that dependancy should be reflected in the
Adam> control
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> Hi
> >>"Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
> Raul> I'm not talking about a complete regression test suite here.
> Raul> I'm talking about simple test cases. If the code dumps core
> Raul> under some condition, reproduce the conditio
Hi
>>"Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
Raul> Manoj Srivastava <[EMAIL PROTECTED]> wrote:
>> Writing regression tests for real is a hard, painstaking effort,
>> often requiring intimate knowledge of the code, and often needs to be
>> tied up with the code itself, changing as the
On 8 Nov 1998, Adam Di Carlo wrote:
> >> The debian-testing group is actually working on this issue as well,
> >> someone should liase with them.
> > Agreed. But I'm at a loss here -- I don't see a debian-testing
> > mailing list, and I don't see any testing links off of the
> > developer's corn
On 6 Nov 1998, James Troup wrote:
> What exactly is the problem with glibc2-dev providing libc6-dev?
> (Apart from the fact that you find it aesthetically displeasing). The
> alpha people do it and it works for them.
There is not any problem with glibc2-dev providing libc6-dev.
[ As I said, we wi
In article <[EMAIL PROTECTED]>, Raul Miller <[EMAIL PROTECTED]> writes:
> Adam Di Carlo <[EMAIL PROTECTED]> wrote:
>> Raul, I really think the proof is in the pudding. If you can help
>> shape a working, easy enough to manage test suite, and start
>> filling that in (even, just start with base pack
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Writing regression tests for real is a hard, painstaking effort,
> often requiring intimate knowledge of the code, and often needs to be
> tied up with the code itself, changing as the source changes.
I'm not talking about a complete regression test
Hi,
I have a package where I wrote a test suite. It is
pkg-order. I think I spent about a fifth of the total time creating
the package in writing the test suite. I don't think I could have
written the tests had I not also been the author of the package.
Writing regression test
Adam Di Carlo <[EMAIL PROTECTED]> wrote:
> Raul, I really think the proof is in the pudding. If you can help
> shape a working, easy enough to manage test suite, and start filling
> that in (even, just start with base packages), we'll be able to look
> at it from there and decide if there's a polic
In article <[EMAIL PROTECTED]>, Ben Gertzfield <[EMAIL PROTECTED]> writes:
James> BTW: this isn't quite right; the source version doesn't
James> necessarily match the version number of the binary packages
James> (e.g. bash && libreadline). Some allowance must be made for
James> this.
> Ahh, so ho
In article <[EMAIL PROTECTED]>, Raul Miller <[EMAIL PROTECTED]> writes:
> Adam Di Carlo <[EMAIL PROTECTED]> wrote:
>> Raul has suggested to add test cases to debian/rules to certify
>> that a bug is gone. As much as I think our documentation should
>> encourage maintainers to write test cases, I be
Daniel Martin <[EMAIL PROTECTED]> wrote:
> Perhaps a "checklist" of manual tests for bugs combined with an
> automated script to check for bugs that can be tested that way (Hmm -
> perhaps a strongly suggested /usr/doc//bugfixlist ?) might be
> an option, but really I'd just prefer to rely on maint
Adam Di Carlo <[EMAIL PROTECTED]> wrote:
> Raul has suggested to add test cases to debian/rules to certify that
> a bug is gone. As much as I think our documentation should encourage
> maintainers to write test cases, I believe this puts undue stress
> on package maintainers. Moreover, if we do not
14 matches
Mail list logo
