From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Subdirectories in package .tar archives Date: Sat, 15 May 2021 17:42:22 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40590"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Emacs developers To: Paul Pogonyshev Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 15 23:43:22 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1li249-000ANZ-NT for ged-emacs-devel@m.gmane-mx.org; Sat, 15 May 2021 23:43:21 +0200 Original-Received: from localhost ([::1]:43776 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1li248-0005On-Q8 for ged-emacs-devel@m.gmane-mx.org; Sat, 15 May 2021 17:43:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37032) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1li23M-0004ds-1q for emacs-devel@gnu.org; Sat, 15 May 2021 17:42:32 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:14259) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1li23I-0006kn-7q for emacs-devel@gnu.org; Sat, 15 May 2021 17:42:31 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id B6CBA8066C; Sat, 15 May 2021 17:42:25 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 53EE680272; Sat, 15 May 2021 17:42:24 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1621114944; bh=YXVI/6Sl2e47kflI8AjujDzNbhYsoGL0HXfbcwGMmbs=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=FQ2TF2z4bEGSl4EYCUYCfjRJUzbcTr5i13QMYg2+hIi4M36dlHz+4h3yPzvCohQJt Eob4xXI9HQnWphNMzXMoRdtYiW6MaxgrF2VUmkY/JgugC0WhLKFAjEApgwXGUuNkzA fe1t+Y12AeDry0u4jjM1Y1jQcQhvdRfzVJnr71HQ4hMvzOhNIZ+yW7/OWSQrXK0EW/ 7lK0ixE/DdTn4ScpDttYbrTR8F5BuCKyR9ZmZCWAAGKnGrLYSkdeTx5nCAZqUGQmZP QNUHvq69nSyPU7luaysXsn02kLvZHMFasQyLAn7lrPYvhKINna0QAChy8KAlgEjfd5 tDDZLzIqefXbA== Original-Received: from alfajor (76-10-140-76.dsl.teksavvy.com [76.10.140.76]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id E3DCB12040E; Sat, 15 May 2021 17:42:23 -0400 (EDT) In-Reply-To: (Paul Pogonyshev's message of "Sat, 15 May 2021 22:20:36 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:269320 Archived-At: > Thank you. So, basically for *resource* files (i.e. not Elisp) and > something unrelated to Info there are no real reasons to avoid > subdirectories, right? Yup. > As long as one can generate packages as expected (probably not with > MELPA, though maybe there is some hidden feature in it for this), I don't know, but at least the specs used for GNU ELPA packages are definitely able to generate tarballs with subdirectories. I'd expect the same holds for MELPA. > they will work fine and one could e.g. do something like > `(defvar ... (somehow-load-resource "foo/bar.baz"))'? Yes. Stefan