Ian Jackson writes:
> I agree. These tests should be shipped with the package source (not
> in the .deb file, since most users won't want them).
I am an active tester. Speaking from this viewpoint, your
proposal is excellent, except for the location of the tests. From my
viewpoint it would
On Thu, 11 Dec 1997, Ian Jackson wrote:
> Philip Hands:
> > It seems a shame to have to ask people to do this sort of thing.
> >
> > It strikes me that one should be able to come up with a script that
> > does a test of this sort in not much more that the time required to
> > write the list (in t
Philip Hands:
> It seems a shame to have to ask people to do this sort of thing.
>
> It strikes me that one should be able to come up with a script that
> does a test of this sort in not much more that the time required to
> write the list (in this simple case at least ;-)
>
> I really think we s
On Thu, 11 Dec 1997, Adam P. Harris wrote:
> "Philip" == Philip Hands <[EMAIL PROTECTED]> writes:
> > It seems a shame to have to ask people to do this sort of thing.
>
> Yes! Maybe even against policy? [Followups on this to debian-policy,
> please.]
We are asking, not requiring. If you don't
>> For example, with the diff package:
>>
>> Package: diff - cmp works on identical and different binary or text
>> files - diff works on files, directories, normal or 2 column -
>> sdiff correctly merges two files - diff3 correctly compares 3 files
"Philip" == Philip Hands <[EMAIL PROTECTED]> w
> On Wed, 10 Dec 1997, Philip Hands wrote:
>
> > > For example, with the diff package:
> > >
> > > Package: diff
> > > - cmp works on identical and different binary or text files
> > > - diff works on files, directories, normal or 2 column
> > > - sdiff correctly merges two files
> > > - dif
On Wed, 10 Dec 1997, Philip Hands wrote:
> > For example, with the diff package:
> >
> > Package: diff
> > - cmp works on identical and different binary or text files
> > - diff works on files, directories, normal or 2 column
> > - sdiff correctly merges two files
> > - diff3 correctly compa
> For example, with the diff package:
>
> Package: diff
> - cmp works on identical and different binary or text files
> - diff works on files, directories, normal or 2 column
> - sdiff correctly merges two files
> - diff3 correctly compares 3 files
It seems a shame to have to ask people to d
[ the orig. message is avail at:
http://www.debian.org/Lists-Archives/debian-devel-9711/msg01597.html ]
Hi everyone,
I haven't heard many responses about the checklist, so I think it's
time to get started. I'd like to do this in several phases:
I. Get a few required packages for comments
On 5 Dec 1997, Karl M. Hegbloom wrote:
> Well, I guess just a checklist outlining things from the policy guide
> is what I had in mind. Like whether it follows the FSSTND or FHS,
> there's a copyright statement, compressed man page, menu file with
> the dwww link and a menu item for X (with s
> "Brandon" == Brandon Mitchell <[EMAIL PROTECTED]> writes:
Brandon> One idea that the testers seemed to like is to create a
Brandon> checklist for checking each package.
It seems to me that a fairly comprehensive set of general guidelines
would be more useful. The checklist format
Andy Mortimer <[EMAIL PROTECTED]> wrote:
> OTOH, if you make this too simplistic, then I fear you're going to miss most
> of the problems: I'm sure the majority of developers do test their packages at
> least a little bit before releasing them. I certainly do. But one of the
> things Debian has bee
In article <[EMAIL PROTECTED]> you wrote:
: This list can be added to by anyone. What I'd like to ask for now is any
: comments on this.
A checklist like this is a good idea, particularly if it eventually provides
the list of things that initially need to be part of a regression suite for
the pa
Brandon Mitchell <[EMAIL PROTECTED]> writes:
>The testers are starting to think about how to organized the 2.0
> testing effort. One idea that the testers seemed to like is to create a
> checklist for checking each package.
[details snipped]
Excellent! If this comes off, I think it will prob
Hello everyone,
The testers are starting to think about how to organized the 2.0
testing effort. One idea that the testers seemed to like is to create a
checklist for checking each package. Before we just checked to see if the
packages installed and if the entire system seemed to work correctl
15 matches
Mail list logo
