You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Alex Chaffee <gu...@edamame.stinky.com> on 2000/10/11 19:46:48 UTC

build organization changes

Comments on code organization.  Please vote so we can change them in
time for the 3.2 release (though if not, then I'd still like to put
them in 3.3).

* I thought we had voted to make the default tomcat home directory
name "tomcat" (instead of "jakarta-tomcat").

  Pro: it would help disambiguate source from binary, it's
	simpler/more straightforward

(If you vote, please say +1 if you want "tomcat," -1 for "jakarta-tomcat")


* The source tarballs should be named jakarta-tomcat-src.tar.gz etc.,
to distinguish them from the binary tarballs, in case someone
downloads both  


* I notice that jakarta-tomcat binary build contains all the Java
source code.  Is there a reason for this?  If not, let's strip the
source files from the binary tarball.


-- 
Alex Chaffee                       mailto:alex@jguru.com
jGuru - Java News and FAQs         http://www.jguru.com/alex/
Creator of Gamelan                 http://www.gamelan.com/
Founder of Purple Technology       http://www.purpletech.com/
Curator of Stinky Art Collective   http://www.stinky.com/

Re: Rename "jakarta-tomcat" to "tomcat" etc. (was Re: build organization changes)

Posted by Hans Bergsten <ha...@gefionsoftware.com>.
Alex Chaffee wrote:
> 
> Looks like this proposal passed.  Unless there are dissenters, can
> someone put these three changes into 3.2?  (Sorry, but I can't take
> the time today.)

How did you come to the conclusion that it passed?  I may have missed
some mails, but on the issue about changing "jakarta-tomcat" to "tomcat"
I count 4 votes against this and only 1 in favor (counting the replies
to "RE: Tomcat 3.2 proposal question", posted by Larry on 10/12).

The other proposals may have passed though; since I don't have a
strong opinion about these I haven't kept track.

Hans
-- 
Hans Bergsten		hans@gefionsoftware.com
Gefion Software		http://www.gefionsoftware.com

Rename "jakarta-tomcat" to "tomcat" etc. (was Re: build organization changes)

Posted by Alex Chaffee <gu...@edamame.stinky.com>.
Looks like this proposal passed.  Unless there are dissenters, can
someone put these three changes into 3.2?  (Sorry, but I can't take
the time today.)

Cheers -

 - Alex

On Wed, Oct 11, 2000 at 02:11:49PM -0700, cmanolache@yahoo.com wrote:
> > * I thought we had voted to make the default tomcat home directory
> > name "tomcat" (instead of "jakarta-tomcat").
> >
> >   Pro: it would help disambiguate source from binary, it's
> >         simpler/more straightforward
> 
> +1
> 
> > (If you vote, please say +1 if you want "tomcat," -1 for "jakarta-tomcat")
> >
> > * The source tarballs should be named jakarta-tomcat-src.tar.gz etc.,
> > to distinguish them from the binary tarballs, in case someone
> > downloads both
> 
> +1
> 
> > * I notice that jakarta-tomcat binary build contains all the Java
> > source code.  Is there a reason for this?  If not, let's strip the
> > source files from the binary tarball.
> 
> I don't think there is a reason for this - some open source packages
> include the source some don't. At that time it wasn't clear if we'll
> have a binary and a source package, and I don't think we had
> nightly builds. Or it just happened by mistake :-)
> 
> +1 on striping the sources from the binary tarball.
> 
> Costin
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org

-- 
Alex Chaffee                       mailto:alex@jguru.com
jGuru - Java News and FAQs         http://www.jguru.com/alex/
Creator of Gamelan                 http://www.gamelan.com/
Founder of Purple Technology       http://www.purpletech.com/
Curator of Stinky Art Collective   http://www.stinky.com/

Re: build organization changes

Posted by cm...@yahoo.com.
> * I thought we had voted to make the default tomcat home directory
> name "tomcat" (instead of "jakarta-tomcat").
>
>   Pro: it would help disambiguate source from binary, it's
>         simpler/more straightforward

+1

> (If you vote, please say +1 if you want "tomcat," -1 for "jakarta-tomcat")
>
> * The source tarballs should be named jakarta-tomcat-src.tar.gz etc.,
> to distinguish them from the binary tarballs, in case someone
> downloads both

+1

> * I notice that jakarta-tomcat binary build contains all the Java
> source code.  Is there a reason for this?  If not, let's strip the
> source files from the binary tarball.

I don't think there is a reason for this - some open source packages
include the source some don't. At that time it wasn't clear if we'll
have a binary and a source package, and I don't think we had
nightly builds. Or it just happened by mistake :-)

+1 on striping the sources from the binary tarball.

Costin


Re: build organization changes

Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
Alex Chaffee wrote:

> Comments on code organization.  Please vote so we can change them in
> time for the 3.2 release (though if not, then I'd still like to put
> them in 3.3).
>
> * I thought we had voted to make the default tomcat home directory
> name "tomcat" (instead of "jakarta-tomcat").
>
>   Pro: it would help disambiguate source from binary, it's
>         simpler/more straightforward
>
> (If you vote, please say +1 if you want "tomcat," -1 for "jakarta-tomcat")
>

-0 ... but I'd rather see the source distro unpack to "jakarta-tomcat-src" in
conjunction with your proposed new name for it.

>
> * The source tarballs should be named jakarta-tomcat-src.tar.gz etc.,
> to distinguish them from the binary tarballs, in case someone
> downloads both
>

+1

>
> * I notice that jakarta-tomcat binary build contains all the Java
> source code.  Is there a reason for this?  If not, let's strip the
> source files from the binary tarball.
>

There is historical precedent within lots of open source projects that you
always get the source with the binaries ... and even the JDK does this to some
degree (src.jar contains the java.* sources but not all the internal
implementation classes).

One (weak but real) argument for keeping the sources is to aid the admin who,
six months from now, is handed the Tomcat binary distribution (having never
seen Tomcat before) and told "make it work" -- and they need the source to
answer questions not covered in the docs.  Yes, they should be able to figure
out where the web site is, but ...

On the other hand, it makes the binary distros somewhat bigger ...

+ 0.5 for stripping.

>
> --
> Alex Chaffee                       mailto:alex@jguru.com
> jGuru - Java News and FAQs         http://www.jguru.com/alex/
> Creator of Gamelan                 http://www.gamelan.com/
> Founder of Purple Technology       http://www.purpletech.com/
> Curator of Stinky Art Collective   http://www.stinky.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org

--
====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat