From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,6df3ec0dff30c185 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!postnews.google.com!u14g2000vbg.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Re: Open source Ada OS? Date: Thu, 27 Jan 2011 01:23:29 -0800 (PST) Organization: http://groups.google.com Message-ID: <2b9d6991-27ef-4bb1-be07-0bd0b7ab78ba@u14g2000vbg.googlegroups.com> References: <4d3f3be3$0$22088$742ec2ed@news.sonic.net> NNTP-Posting-Host: 137.138.182.236 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1296120210 31923 127.0.0.1 (27 Jan 2011 09:23:30 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 27 Jan 2011 09:23:30 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: u14g2000vbg.googlegroups.com; posting-host=137.138.182.236; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10,gzip(gfe) Xref: g2news1.google.com comp.lang.ada:16728 Date: 2011-01-27T01:23:29-08:00 List-Id: On Jan 27, 12:02=A0am, "Randy Brukardt" wrote: > if you treat those as *one* project, then you lose the ability > to have separate releases for different part of the project. Huh? Sorry, but this is nonsense. Nobody forces you to compress the whole repository as a method for making a "release". If this feature is supported by VCS, it is for convenience, but certainly not obligatory. What I do in such a case is a separate release script that builds the deliverable packages from what is available in the repository. Many such scripts can exist together without any problem to address the case you describe (hint: these scripts can and should be versioned together with everything else), and as well the repository can contain stuff that is not supposed to be released at all. Did I mention that such a script can also make some last-second automated modifications to the package, like generating docs or sticking appropriate license to all source files for multi-licensed projects? In general, the concept of making a "release" by just compressing the whole repository is simplified to the point of being useless. This seems to be a common practice in many open-source projects, but I'm surprised by that. > Merging, however is never a solution. I agree. I use it for the fast-forward type of merging, where files are not modified and only the logical progress is made, but I don't trust the "automated-editing" type of merge. The overhead of further verification is equivalent to manual editing anyway. -- Maciej Sobczak * http://www.inspirel.com