Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0EDE941DC for ; Tue, 21 Jun 2011 07:38:47 +0000 (UTC) Received: (qmail 68218 invoked by uid 500); 21 Jun 2011 07:38:47 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 68073 invoked by uid 500); 21 Jun 2011 07:38:45 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 68055 invoked by uid 99); 21 Jun 2011 07:38:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jun 2011 07:38:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gstein@gmail.com designates 209.85.210.47 as permitted sender) Received: from [209.85.210.47] (HELO mail-pz0-f47.google.com) (209.85.210.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jun 2011 07:38:37 +0000 Received: by pzk36 with SMTP id 36so4680138pzk.6 for ; Tue, 21 Jun 2011 00:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=m4QbAMpiLFJwdQ3dHDivZnyOMalEtx35nMqBQnaDUag=; b=eRlSP9zLsMCmmQ1foA243SCeHkNGygR+v8qUwcGiwY9vnrDDQeVUj4UGSpWTIbbKAq /e/JEea9/eNOloXRaxC2BY/0rqDPqPrMPzAvC2UdedIw6pUOdOt5fc9MjIDEQ5wpIA2F JKlHfsUqA3hlqboSbjFpRt5CnQn476ofgZkfc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=TAeVnXyKqkFhNwTIEIhXUuFJins+bhsbzXX76Tv34a8ke7Vsmdgr3Y8JPCq/esWIEw Vs4QAXJZbzKN1e7ewxQqpINeMOUkMkQo2sDldJl4kQ2NdYYYF4pfAEP2ACwDd6RYNLpZ oNQiJ+7Xlu78lvBIRRBsIxUYuVqJ+PWp+ihn0= MIME-Version: 1.0 Received: by 10.142.253.20 with SMTP id a20mr1178210wfi.190.1308641895782; Tue, 21 Jun 2011 00:38:15 -0700 (PDT) Received: by 10.143.63.6 with HTTP; Tue, 21 Jun 2011 00:38:15 -0700 (PDT) In-Reply-To: <4E0049B3.4090709@gmx.net> References: <4E003E75.5020106@gmx.net> <4E0049B3.4090709@gmx.net> Date: Tue, 21 Jun 2011 03:38:15 -0400 Message-ID: Subject: Re: Files generated by Visual Studio From: Greg Stein To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Jun 21, 2011 at 03:35, Mathias Bauer wrote: > On 21.06.2011 09:03, Greg Stein wrote: >> >> If these files are generated, then why even put them into source >> control? They can simply be generated on each developers' machine as >> part of the build. >> >> Am I missing something? > > This would be a PITA for all developers, especially for those creating > releases. You can't tell them: here's the source, grab Visual Studio and use > it to create some more files before you can build the stuff. > > Besides that, there are no project files to create them from. And it's also > possible that these files have been modified in the past. > > We don't use Visual Studio for the build, only the compiler. So we don't > want to rely on its usage. > > It may be uncommon at Apache (perhaps even unwanted) to commit generated > files, but nevertheless my recommendation is to allow to make them part of > the software grant if that is legally possible. Everything else can be > discussed later. Not a problem. We're just talking about different types of "generated files". I'm concerned about "build outputs", but these are wizard outputs from the various VS tools. They are one-time outputs, rather than part of the build process. Thanks for the clarification! Cheers, -g