This is the mail archive of the
mailing list for the GCC project.
Re: dejagnu version update?
- From: Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>
- To: Mike Stump <mikestump at comcast dot net>,Ramana Radhakrishnan <ramana dot radhakrishnan at foss dot arm dot com>
- Cc: Andreas Schwab <schwab at suse dot de>,Jeff Law <law at redhat dot com>,David Malcolm <dmalcolm at redhat dot com>,gcc-patches List <gcc-patches at gcc dot gnu dot org>,GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 16 Sep 2015 20:49:58 +0200
- Subject: Re: dejagnu version update?
- Authentication-results: sourceware.org; auth=none
- References: <1441916913-11547-1-git-send-email-dmalcolm at redhat dot com> <1441916913-11547-3-git-send-email-dmalcolm at redhat dot com> <55F720E6 dot 7020709 at redhat dot com> <4CB1399A-23A6-44F7-A25F-ECBD953E03A0 at gmail dot com> <55F74C3D dot 50504 at redhat dot com> <F5F4A096-2DD7-4635-9CB2-5A611247D71F at comcast dot net> <1B14D92A-0476-416B-A80D-A3083383C48D at gmail dot com> <55F879CB dot 2090607 at redhat dot com> <16565ACE-A56C-4971-BEA9-B299C9B40346 at comcast dot net> <mvmfv2eesa5 dot fsf at hawking dot suse dot de> <2BAFA587-8192-495C-B98C-BDA442B1A8A6 at comcast dot net> <55F997E3 dot 7030508 at foss dot arm dot com> <76A129A1-BF21-44BA-BC8C-09CC2E72AED1 at comcast dot net>
On September 16, 2015 7:57:03 PM GMT+02:00, Mike Stump <firstname.lastname@example.org> wrote:
>On Sep 16, 2015, at 9:25 AM, Ramana Radhakrishnan
>> Sorry about the obvious (possibly dumb) question.
>> Can't we just import a copy of dejagnu each year and install it as
>part of the source tree?
>We could, and indeed, some people do engineering that way. We instead
>depend upon package managers, software updates and backwards
>compatibility to manage the issue. This is generally speaking, a
>better way to do software. In the olden days, back before shared
>libraries, X11 was the straw that broke the camels back.
[Well some thus later had KGI, GGI and fresco (the interviews thing), but that's another story for sure ;) ]
Either way. Importing doesn't make sense at all.
Establishing and maintaining duplicated gcc_load_lib cascades don't either IMO. If folks feel maintaining them is less hazzle than forcing a new dejagnu then fine with me (although we do require pretty recent libs anyway and developers will usually likewise use rather recent binutils et al for obvious reasons).