From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: feature/package-vc has been merged Date: Mon, 07 Nov 2022 14:07:00 +0200 Message-ID: <83bkpjynmj.fsf@gnu.org> References: <164484721900.31751.1453162457552427931@vcs2.savannah.gnu.org> <875yg1bc02.fsf@posteo.net> <878rkxgpms.fsf@posteo.net> <87sfiyk3a2.fsf_-_@posteo.net> <838rkp4ptj.fsf@gnu.org> <87zgd58i7y.fsf@posteo.net> <83k0492u5i.fsf@gnu.org> <87fsew8g18.fsf@posteo.net> <83mt941cyd.fsf@gnu.org> <87fsewp0ec.fsf@posteo.net> <837d0814c9.fsf@gnu.org> <878rkooz1o.fsf@posteo.net> <831qqg1306.fsf@gnu.org> <874jvcowzm.fsf@posteo.net> <83y1soypvx.fsf@gnu.org> <87y1song5x.fsf@posteo.net> <83v8nsyof7.fsf@gnu.org> <87leoond7l.fsf@posteo.net> <83r0yfzz01.fsf@gnu.org> <87bkpjyx3p.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14869"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, rms@gnu.org, emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 07 13:08:24 2022 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 1os0vO-0003es-Py for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Nov 2022 13:08:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1os0uW-0001EY-0a; Mon, 07 Nov 2022 07:07:28 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1os0uO-000181-Mo for emacs-devel@gnu.org; Mon, 07 Nov 2022 07:07:20 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1os0uM-0003Ig-DN; Mon, 07 Nov 2022 07:07:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=b972XOoDuIUN1CWOYAYS6+nDEjEjQvEsfx5PafDa3Ek=; b=i5ZIowb5R9GS NCID5BQxwluJHt+x7zqTx4ckcViN/jCvgteUtDf3gFzkYZau0FYxizuO4bImspTTUKSVG0R8VYk43 /EfWAxs5nM4jnWE3TQGOeQYpUytYo3gRajkMcbxfSaloKtcmEX4eB1joaYo4R66lWsk3mtFjnQKFf F0efSuJ5tmqhUol8TeuJ2HBriYK8fJSIHt7WZhzWOMZhXP6Ex4S2PlImSJZqODs/GgZcJGeAYPgqC pFuPJXtbf7B06+hmztamw2cInAhgd/ggnuXBjPLQoVuUzOGL3UOS+0OoeHabnvtTJZ34UC0jUOI3a ukO+dBAyVMBly04gx3NtnQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1os0uL-00044J-7o; Mon, 07 Nov 2022 07:07:17 -0500 In-Reply-To: <87bkpjyx3p.fsf@posteo.net> (message from Philip Kaludercic on Mon, 07 Nov 2022 08:42:18 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299291 Archived-At: > From: Philip Kaludercic > Cc: monnier@iro.umontreal.ca, rms@gnu.org, emacs-devel@gnu.org > Date: Mon, 07 Nov 2022 08:42:18 +0000 > > Eli Zaretskii writes: > > >> From: Philip Kaludercic > >> Cc: monnier@iro.umontreal.ca, rms@gnu.org, emacs-devel@gnu.org > >> Date: Sun, 06 Nov 2022 18:35:10 +0000 > >> > >> Eli Zaretskii writes: > >> > >> > And if you think many do, why not clone the repository directly into > >> > ~/.emacs.d/elpa/? > >> > >> Because that won't take care of scraping for autoloads, byte > >> compilation and installing missing dependencies. > > > > I don't see why. Please elaborate how having the repository inside > > ~/.emacs.d gets in the way of these activities. > > It doesn't get in the way, the issue just is that if you were to just > clone a package right into .emacs.d, you would still have to do all > these steps individually and manually. Which steps are those, and why do we have to do it manually? > >> You mean as in only allowing for packages to distribute lisp code in the > >> root directory of the repository? That would pointlessly break too many > >> packages that decide to structure their file hierarchy for whatever > >> reason. > > > > Is that what :lisp-dir is about? then the doc strings in package-vc.el > > doesn't even hint about that. In particular, there's nothing there > > about the root directory of the repository. > > The docstring for `package-vc--archive-spec-alist' has the following > (I'm still looking for a better way to document this): > > `:lisp-dir' (string) > The repository-relative name of the directory to use for loading the Lisp > sources. If not given, the value defaults to the root directory > of the repository. Ah, it's a misunderstanding. See below. > > (Not that I understand > > why having Lisp files in a subdirectory of the repository would be a > > problem that needs an explicit configuration of the package, probably > > missing something else again.) > > Maybe I am mistaken, but having a directory in `load-path' doesn't mean > all sub-directories are automatically indexed, right? We have a standard solution for that: normal-top-level-add-subdirs-to-load-path. We install in any directory that needs this a file called subdirs.el with the following contents: (if (fboundp 'normal-top-level-add-subdirs-to-load-path) (normal-top-level-add-subdirs-to-load-path)) Example of directories which need this is the site-lisp directory. Why cannot we do something like this in this case?