You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2002/06/18 10:54:16 UTC

Reminder; test/ directories in roll release script

We are still failing to cull out

   /test/
   /modules/test/
   /srclib/apr/test/
   /srclib/apr-util/test/

Cliff had already rolled the package when we noticed, and we didn't
consider this enough of a showstopper to junk them all.  But it would
be good to clean them out as part of our tag and roll shell script.


Re: Reminder; test/ directories in roll release script

Posted by Cliff Woolley <jw...@virginia.edu>.
On Tue, 18 Jun 2002, Aaron Bannert wrote:

> Why shouldn't we be including these in our tarballs? They are perfectly
> valid, IMHO. They don't get built automatically, and they give our
> users something to point at if something breaks. (Also extremely
> useful as a source of example code).

I totally agree.  That's why my heart wasn't broken that they were still
in there for 2.0.39.  :)

--Cliff


Re: Reminder; test/ directories in roll release script

Posted by Aaron Bannert <aa...@clove.org>.
On Tue, Jun 18, 2002 at 03:54:16AM -0500, William A. Rowe, Jr. wrote:
> We are still failing to cull out
> 
>   /test/
>   /modules/test/
>   /srclib/apr/test/
>   /srclib/apr-util/test/
> 
> Cliff had already rolled the package when we noticed, and we didn't
> consider this enough of a showstopper to junk them all.  But it would
> be good to clean them out as part of our tag and roll shell script.

Why shouldn't we be including these in our tarballs? They are perfectly
valid, IMHO. They don't get built automatically, and they give our
users something to point at if something breaks. (Also extremely
useful as a source of example code).

-aaron