From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 91AD93858D20 for ; Wed, 31 May 2023 23:04:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 91AD93858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1685574295; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=aflQ03PAnlSbrsqkmtcUSjIg5C8yrCuMo3PtMa06S7g=; b=gbh+R2wSUtvdmSHv7OTYmWxI2k419jxvm75fF4kdF4A+c637MeHO02e8cZqsgwQPoFhzbh 0XzROjMTxYr/OxVk/RTYDrsjnqgEqTNUG2qU3Hd3yiMEt3whxj40O9CkqHvV6wvEagamRb WOt7qQFQk164XJDLiSfCRjcbHbS4DAU= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-488-3TDYZRxpPjW8lIuJXl8JHQ-1; Wed, 31 May 2023 19:04:52 -0400 X-MC-Unique: 3TDYZRxpPjW8lIuJXl8JHQ-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A25D9101A531; Wed, 31 May 2023 23:04:51 +0000 (UTC) Received: from redhat.com (unknown [10.22.8.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 94241140E95D; Wed, 31 May 2023 23:04:51 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1q4Us6-0006Hd-QX; Wed, 31 May 2023 19:04:50 -0400 Date: Wed, 31 May 2023 19:04:50 -0400 From: "Frank Ch. Eigler" To: Daniel Thornburgh Cc: elfutils-devel@sourceware.org Subject: Re: Local Build ID Directory Lookup (DEBUGINFOD_LOCAL_PATH) Message-ID: <20230531230450.GD26841@redhat.com> References: <20230531223555.GC26841@redhat.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi - > Ah, I had forgotten completely that file URLs worked out of the box > (libcurl, duh). Yeah. > When we tried that way back when, the issue was just that it > actually does a libcurl fetch out of that path and saves another > copy of the file into the cache. Yes, a copy is made. This is "traditional" in the sense that the client code ensures that even if an original upstream server goes away, cached files stay accessible for a while. I can also see how this might be less valuable than just getting at the files with minimum overhead. Does anyone think we need to have both as options? - FChE