From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83430 invoked by alias); 13 Jun 2017 17:47:14 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 83376 invoked by uid 89); 13 Jun 2017 17:47:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=our X-HELO: mail-wr0-f173.google.com Received: from mail-wr0-f173.google.com (HELO mail-wr0-f173.google.com) (209.85.128.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 13 Jun 2017 17:47:09 +0000 Received: by mail-wr0-f173.google.com with SMTP id v104so145147321wrb.0 for ; Tue, 13 Jun 2017 10:47:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8qFo8w5rybRStbysIocmFiAXdUBmBSVAf+ykEjx527o=; b=DCa74Uinp45BnlbMEMn0GJiAtKNRPSDfJdnlnMKAUgJ7TBfm5chpg9gtNrZmY4TEVZ iZNmHWrOF5V3kVaXnUiBGwPlY+oIc9lJclfadAU7yVhdkVojfndy2Y4qlQp8BmEeWljN 1eZs+GIGiiIOZjjM5cQKengdUlH4X/kCEI4PFEOXnt7Mn+GU81hA+TKQUVTmHq2RRZqT GFjltl21RadfJQ2w9F0KfWOsK9Kt0W9LRKyPm+2saXaAZeRxWCVJO6ExqXrzg87xqqmV zjI6BDggnlKnFErrMpuutst7FkLtju2fOmlTLpreiHcIyS5NoJEuQyNDSq4KuWDaqoMc wCNg== X-Gm-Message-State: AKS2vOx7RGAtZ15V4R0urv4G0X8H61H0A9jXjkeR5NaVScLazoJH1gS8 4FHUzCWX4Tw2ruwPQXhcIaEaMqOuxA== X-Received: by 10.80.136.110 with SMTP id c43mr775707edc.171.1497376031647; Tue, 13 Jun 2017 10:47:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.164.185 with HTTP; Tue, 13 Jun 2017 10:47:11 -0700 (PDT) In-Reply-To: <27c866069cdcc4dc4b5e3cf5d3affe83@polymtl.ca> References: <227db26304444bfb5ed8f699ab67e7fd@polymtl.ca> <87o9tsozn6.fsf@pokyo> <83ink03q1w.fsf@gnu.org> <27c866069cdcc4dc4b5e3cf5d3affe83@polymtl.ca> From: Matt Rice Date: Tue, 13 Jun 2017 17:47:00 -0000 Message-ID: Subject: Re: [PATCH] Fix python compatibility with old versions of GDB To: Simon Marchi Cc: Eli Zaretskii , Tom Tromey , orgads@gmail.com, "gdb-patches@sourceware.org" Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-06/txt/msg00398.txt.bz2 On Tue, Jun 13, 2017 at 10:29 AM, Simon Marchi wrote: > On 2017-06-13 16:44, Eli Zaretskii wrote: >> >> FWIW, I always configure GDB to use a version-specific data-directory, >> because I leave old GDB versions (renamed) on my system, so I could >> still use them after installing a new version. E.g., if the new >> version turns out to have a bug. I would actually be happier if we >> changed our installation scripts to do that by default, because the >> scripts are almost never backward-compatible IME. > > > Can you give more details on what you think could/should be done by default? > > For such a use case, I would compile each gdb with a separate prefix (e.g. > --prefix=/opt/gdb/), which would give each install its own data > directory. So from my point of view, the "feature" is pretty well-covered. Is there any argument against appending version to the data-directory by default? e.g. gcc configures /usr/lib/gcc/triplet/version? I see a number of /usr/share/*/[0-9]\.* directories here.