From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Shitikanth Newsgroups: gmane.emacs.bugs Subject: bug#55655: 28.1; package.el no longers respects `user-emacs-directory' Date: Fri, 27 May 2022 10:40:53 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7836"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 55655@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri May 27 07:12:14 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1nuSGk-0001s5-BA for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 27 May 2022 07:12:14 +0200 Original-Received: from localhost ([::1]:32978 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nuSGi-0001VS-Ok for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 27 May 2022 01:12:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55220) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nuSGY-0001T2-6j for bug-gnu-emacs@gnu.org; Fri, 27 May 2022 01:12:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38472) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nuSGX-0003Wn-SA for bug-gnu-emacs@gnu.org; Fri, 27 May 2022 01:12:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nuSGX-0001Si-KR for bug-gnu-emacs@gnu.org; Fri, 27 May 2022 01:12:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Shitikanth Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 27 May 2022 05:12:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55655 X-GNU-PR-Package: emacs Original-Received: via spool by 55655-submit@debbugs.gnu.org id=B55655.16536282695559 (code B ref 55655); Fri, 27 May 2022 05:12:01 +0000 Original-Received: (at 55655) by debbugs.gnu.org; 27 May 2022 05:11:09 +0000 Original-Received: from localhost ([127.0.0.1]:60602 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nuSFh-0001Rb-DW for submit@debbugs.gnu.org; Fri, 27 May 2022 01:11:09 -0400 Original-Received: from mail-pj1-f46.google.com ([209.85.216.46]:36830) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nuSFf-0001Qa-8I for 55655@debbugs.gnu.org; Fri, 27 May 2022 01:11:07 -0400 Original-Received: by mail-pj1-f46.google.com with SMTP id u12-20020a17090a1d4c00b001df78c7c209so6204807pju.1 for <55655@debbugs.gnu.org>; Thu, 26 May 2022 22:11:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lV7JulkOSjSrV8GuDqKw4k65y4uA5LMdxriWsXWaP8c=; b=V287PfaG5/SP7HSWMsyqiuC4dbnUj/uUBPXBW7sVZDSKoRbS4umzuR+qDm9VigvpVe KYqtl1RWEj6SAempXDXtold2Zt/8zbRsKTHZ6SV/9iMNzSK8TvdDpCYBIq+bYVksXCZQ mD3OxNchoBP4f+Qk49nHHAMFXg3AAy3//sDdT4g95WrNDX7RPVa+wJMtBqnYTqS36/sf Dt54HhXUSXSiTtELXsMsNbmAFMSY3/aOwecAt8ZdagZNKiNQg9NbrRkxEPyuJ8Wj4I5a 3mogaGyed8ou73I1jEC3f+JS/Vy50iSeFtshkQvVClX6+MQVkpK/DxIeCsXBFwD2B1Jm n2yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lV7JulkOSjSrV8GuDqKw4k65y4uA5LMdxriWsXWaP8c=; b=DI5syiz0VBtVjqJ9khGWvL7qwYazA1SzggwNjM1Ju1+3/S+VsDdB443el8pRiT2K1/ weFu7wvvsgXIQHFVM4G/HwIkqiwzvJtF3ZdDBvzqEkKEVSqredvF7lRY+O4wekmrkA1x ooCP/U0V0fVNiYTbDSqP/6bSxdONMs/YZ6IU8ogzweO9PGu3BzPlu+AKR85xHSLawfiV LhXpfxjv4SEbBTKefRXIG47iBhAUO2akf+RIK1ilyCfjo279CAF18tZNa9poHOljbgfe k5GWrw35KmD3hJHlFNYFUzUgzxFMba+ndz92OclHDYL0xCv0PzVOXCEqS7sMr20hc4gC TgJA== X-Gm-Message-State: AOAM533Xq327HwJzaQcShAdJ+8SveBIgo1Ph4WRqSkMRUuITVjCNS8XA wz4YW+h/koANeMEnuIedwBPHDuQY6Ydu4daXBtVsHhfbgVs= X-Google-Smtp-Source: ABdhPJyuAt/ZsfaV8h4r2/WxdQ2ssH899eCc9dGDcIjJXU1btp/eVT9P+LzmDb2+iSVlr/u3B6DPP9+BaShjMZv5GLg= X-Received: by 2002:a17:902:b688:b0:162:3124:cde2 with SMTP id c8-20020a170902b68800b001623124cde2mr20983840pls.166.1653628261065; Thu, 26 May 2022 22:11:01 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:233142 Archived-At: >Could you give some more details about the use case that actually affects you I just have a couple of different configs and use them with "emacs -Q --load $config_dir/init.el" and set the user-emacs-directory early in "$config_dir/init.el". This was also the easiest way to try out other people's configs without disturbing your own. I guess I was always aware that this was an abuse of the init system, so if this is an intended change, you can close the bug report. On Thu, 26 May 2022 at 20:59, Stefan Monnier wrote: > > Shitikanth [2022-05-26 16:37:48] wrote: > > Until emacs 27.2, package.el used to correctly pick `package-user-dir' > > based on the value of `user-emacs-directory', but it now seems to ignore > > it and defaults to "~/.emacs.d/elpa". > > > > Demo: > > (setq user-emacs-directory "/tmp") > > (require 'package) > > (message "%s" package-user-dir) > > > > Starting with "emacs -Q" this would output "~/.emacs.d/elpa". > > Expected output: "/tmp/elpa" (as in emacs 27.2). > > That expectation is wrong, sadly, because it assumes that the > initialization of `package-user-dir` takes place during (require > 'package), which is not the case because that variable is now > initialized earlier. > > I understand it's a change, but it might be difficult to make this > specific recipe work the way you want without breaking other use-cases. > > Could you give some more details about the use case that actually > affects you (I hope it's slightly different from the simplified recipe > shown above)? > > > Stefan >