Re: What's Debian's /usr/src policy.

1997-12-28 Thread bhmit1
On 26 Dec 1997, Rob Browning wrote:

> The question is, "who owns /usr/src, Debian or the local sysadmin?"

I'm not the official word on this but I think Debian "owns" everything but
/usr/local (in which it can only make a directory).  There are exceptions
if your directory isn't in the file system standard (don't remember the
correct abreviation).  However, I recently saw a nice behaviour from a
Sun.  Before clobbering a file that Sun didn't "own" (in another package),
it prompted me on what it was about to do, by asking if I wanted to
clobber them.  This would be a nice addition in dpkg/deity.

Thanks,
Brandon

-
Brandon Mitchell <[EMAIL PROTECTED]>   "We all know linux is great... it
PGP: finger -l [EMAIL PROTECTED]  does infinite loops in 5 seconds"
Phone: (757) 221-4847  --Linus Torvalds


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Checklist request

1998-01-03 Thread bhmit1
Hello everyone,

--
BACKGROUND AND CURRENT STATUS:
--

Ok, I'm finally ready to start doing this.  For those that are reading
this for the first time, the checklist will be used by the testers to
verify a package is working correctly.

Scripts welcome (I finally gave in) in /usr/doc//testme.sh .
Non-maintainers can send scripts to me (cc the maintainer), and I'll put
them on the web page when it's put together.

The Debian Testing Group encouraged to modify any scripts and save
them for package testing in the future.  When submitting a list, please
try to include things any user can do, e.g. don't require the package 
source or an external program that is difficult to obtain.

My personal intention is to make a testing directory containing a
sub-directory for each package, and use a shell script with diff to run
and verify the testing scripts in each directory.  Hopefully this just
means a huge one time setup cost for me.

Here's the list after my first small request:

-
EXAMPLES:
-

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

Package: grep
- Maintainer uses khadaffy test-set.
- Try a bunch of greps using different search patterns
- Also try -v switch.

Package: gzip
- These will be tested by dpkg itself
- verify compression works
- verify uncompression works

Package: tar
- These will be tested by dpkg itself
- create a compressed tarball and verify contents

-
YOUR MISSION:
-

What I'm asking for new is checklist for any package in main, however, try
to focus on required or at least standard packages in the beginning.  I'm
also opening this up to non-maintainer submissions, but cc the maintainer
if you do this.  Additions to the current list are welcome.  As these come
in, I'll post a change log to the testing and devel list, and point
interested readers to the online location (which isn't quite ready yet).

Please use the above subject line and send them directly to me so we don't
accidentally flood the mailing list (and cc the maintainer if
appropriate).

Thanks to all the supporters, this is going to be a big job, and I'll
need all the help I can get.

Happy New Year!
Brandon

-
Brandon Mitchell <[EMAIL PROTECTED]>   "We all know linux is great... it
PGP: finger -l [EMAIL PROTECTED]  does infinite loops in 5 seconds"
Phone: (757) 221-4847  --Linus Torvalds


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: Debian 2.0 release requirements

1998-01-08 Thread bhmit1
Attention all package maintainers:

Just a note that the testing group would like to have an idea of how to
test the individual packages (before we were only seeing if it would
install).  All we are asking for is a checklist (and a script if you
want), which in the most general sense says: "this program should do this,
that program should do that".  Please send them to my email, with the
subject "Checklist request" (so I can sort them out).  If you've missed
the previous messages about this, just drop me a line and I'll give you
the full details and an example.

Thanks,
Brandon

-
Brandon Mitchell <[EMAIL PROTECTED]>   "We all know linux is great... it
PGP: finger -l [EMAIL PROTECTED]  does infinite loops in 5 seconds"
Phone: (757) 221-4847  --Linus Torvalds


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .



Re: Debian 2.0 release requirements

1998-01-08 Thread bhmit1
On Thu, 8 Jan 1998, Vincent Renardias wrote:

> On Wed, 7 Jan 1998 [EMAIL PROTECTED] wrote:
> 
> > Just a note that the testing group would like to have an idea of how to
> > test the individual packages (before we were only seeing if it would
> > install).  All we are asking for is a checklist (and a script if you
> > want), which in the most general sense says: "this program should do this,
> > that program should do that".  Please send them to my email, with the
> > subject "Checklist request" (so I can sort them out).  If you've missed
> > the previous messages about this, just drop me a line and I'll give you
> > the full details and an example.
> 
> If such scripts are written, I suggest they are run from debian/rules at
> package build time. (some packages already do this (some perl modules for
> example)) This way, testers will be able to focus their attention on
> things that can NOT be done automatically...

A request similar to this was already made, and decided against.  I don't
expect the maintainer the build the package on multiple setups, which is
what we are testing. Also, if there is not easy access to the scripts,
they will not be used by the testers (we don't have the time to download
the sources and binaries for all these packages).  The testers are urged,
but not required, to consider the scripts as templates, or rough ideas, of
how to set up their own scripts (therefore we get some individual test).  

Final note, the scripts are _optional_.  It took a bit of convincing to
get me to agree with that part of the idea.  But I think there can be
benifits over the checklist only aproach.

I'm hoping this will be easier to understand once I get things organized
and start posting periodic updates and put up the web site.

If you have any other questions, feel free to ask,
Brandon

-
Brandon Mitchell <[EMAIL PROTECTED]>   "We all know linux is great... it
PGP: finger -l [EMAIL PROTECTED]  does infinite loops in 5 seconds"
Phone: (757) 221-4847  --Linus Torvalds



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .