Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 3250 invoked from network); 14 Jun 2007 18:23:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jun 2007 18:23:25 -0000 Received: (qmail 26200 invoked by uid 500); 14 Jun 2007 18:23:26 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 26142 invoked by uid 500); 14 Jun 2007 18:23:26 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 26125 invoked by uid 99); 14 Jun 2007 18:23:26 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jun 2007 11:23:26 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of sebbaz@gmail.com designates 64.233.162.234 as permitted sender) Received: from [64.233.162.234] (HELO nz-out-0506.google.com) (64.233.162.234) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jun 2007 11:23:22 -0700 Received: by nz-out-0506.google.com with SMTP id 14so578236nzn for ; Thu, 14 Jun 2007 11:23:01 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ImxsEjF2dDzTfj2iUo9xhtim2A5QbeNWt9d4yZ3MOfbuzwxZLspltEud5NGkgdDl4FExy0i+WqkE8aR47XVm+Wc4ImLrqQ7UcK77vGqH9Csp0kR3boGQjZpJQZPXeoFmGbbTtxeZjvGl4B94CztdSYVr+OI1IvNxr+UIsK6z5bQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=otXE0Fw4BvC6NUefxHK0HUQzPKFWxhliLnjzL3IgigZjkF/ZZV4ZEfisZYSGjrpN3ENPFdQ9nJQg1+2bB04Fb5vdS4akO0+Db6AjiOIu8z5BJMIQn+aUMH8wIvT0QrYIjO/XAamM9EqlyahTlaq4NleCbByRrtRg8fXwgW7KNNw= Received: by 10.114.92.2 with SMTP id p2mr2090641wab.1181845381222; Thu, 14 Jun 2007 11:23:01 -0700 (PDT) Received: by 10.114.168.12 with HTTP; Thu, 14 Jun 2007 11:23:01 -0700 (PDT) Message-ID: <25aac9fc0706141123r717329aeg41e214e886f18912@mail.gmail.com> Date: Thu, 14 Jun 2007 19:23:01 +0100 From: sebb To: "Jakarta Commons Developers List" Subject: Re: [vote] releasing jci RC3 as 1.0 ...maybe this time? In-Reply-To: <4670575A.9090908@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8a81b4af0706032149je07403cxbaff8cf9ad987435@mail.gmail.com> <8a81b4af0706041759s5afe4db4k32087c64dfb4793a@mail.gmail.com> <73385F21-665E-4401-9C37-C35F85FEB439@apache.org> <466C30F6.3030105@free.fr> <6543E6A6-2370-4BFC-BE8E-23048B9DBD39@apache.org> <4670575A.9090908@free.fr> X-Virus-Checked: Checked by ClamAV on apache.org On 13/06/07, Luc Maisonobe wrote: > Torsten Curdt a =E9crit : > >>> But seriously: be realistic. Those people building the releases from > >>> will have subversion on their machine. And what can be simpler than a > >>> one-liner to checkout the sources? Even downloading it from an apache > >>> mirror is more work. > >> > >> People may have subversion but may not be able to use it. > >> > >> For example, I cannot use svn (nor cvs for that matter) through my > >> corporate firewall. > > > > Wait a sec - you cannot use http from your development machine? > > http is fine from browsers that handle proxy with username/password, > https was allowed only recently and may be shut down at any time, svn, > ssh, cvs pserver are all filtered. > Configuring svn clients to handle proxy username/password is not > straightforward. For command-line svn it is handled by the user > configuration file for servers, not by command-line options. I don't > know about graphical clients or IDE embedded clients. > > I also know another company where http filtering is more strict, with > files without any extension suppressed, files with some extensions > suppressed, files modified on the fly to comply with some rules, > user-agent is checked to allow only certified browsers to connect ... > For example on this network, these so called =AB security rules =BB > prevented me from downloading security upgrades for Debian computers > (which are simple binary files downloads on an http server) ... > > > > >> When I need a package that is only available by > >> checking out from its repository, I have to check it out from home, pu= t > >> it on an USB stick and copy it the next day at work. It is very > >> inconvenient. > > > > That's a truly sad story ...but we cannot provide a good solution for > > every awkward workplace. > > I agree this is weird and cannot be generalized. I also agree that in > the Apache case, this can be circumvented as anonymous access to the > subversion server is http-based. I only wanted to point out that since a > version control system is not a publication system, using it for that > purpose may be tough for some people. > > > What would you think - how many percent of the developers that require > > to build a project from the source have no http access to the internet? > > Well, for jci I will personally send them a tar of the checkout - if > > they have email :-p Source is not only needed for building the binary; it's also useful to have access for debugging purposes in IDEs. > I would only advise to have a simple and classical way to distribute: an > archive on a web server people can retrieve using a web browser. +1 > Well, this is only my view and it is probably distorted, you can ignore i= t. It's my view too. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org