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: Sun, 06 Nov 2022 21:03:42 +0200 Message-ID: <83r0yfzz01.fsf@gnu.org> References: <164484721900.31751.1453162457552427931@vcs2.savannah.gnu.org> <87edupbdp0.fsf@posteo.net> <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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23682"; 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 Sun Nov 06 20:04:46 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 1orkwn-0005xi-HP for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Nov 2022 20:04:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1orkw6-0004hS-Bf; Sun, 06 Nov 2022 14:04:02 -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 1orkw4-0004hE-Py for emacs-devel@gnu.org; Sun, 06 Nov 2022 14:04:00 -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 1orkw4-0004yq-Ha; Sun, 06 Nov 2022 14:04:00 -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=MhuIGjWShRGbzZPYpoFZesBMFDSbgDQv4Lw5XaX/IZg=; b=cgMIQ6Mz4jYS xL1Sj7RbS3mA5580QVPDMXB9lILduZN0hG2aAyurQwBGBwFaNxZaA0n9dy+GQgQi4WIK17YjnyNNM uJj3uBmvAkMQ5N4ld0eqZdDMlTdnAwP8IYaMIJhOSx+2OpCNhJdWdAyDj+K3OW2WKd2xfwYOixJ6N RzhuIHdFonNrikr0H4Vfwm++VN2rH4fNLNWK2tShQLZ6kEP29QvS9mLR7fVlHu41bHJeZqnGZvTBZ HgrGbxCO9LlYKlf3Q6E0mfxzOQE0Oa3PYTjayq+x/l+dPsflnsOgk5GTUqwCkG7EBjRDF5OiaNXps 88Qv/6ECOm0Fkg+G8WpXag==; 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 1orkw2-0001Ns-Nd; Sun, 06 Nov 2022 14:03:59 -0500 In-Reply-To: <87leoond7l.fsf@posteo.net> (message from Philip Kaludercic on Sun, 06 Nov 2022 18:35:10 +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:299269 Archived-At: > 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. > >> All of this would only apply to packages with external `:lisp-dir's, > >> which doesn't immediately interest a user/developer. Having to keep > >> this in mind would pointlessly expose an internal detail of package-vc > >> that I'd like to avoid. > > > > But it is us who introduced and support :lisp-dir. If we think it's a > > leaky abstraction, we could decide not to support it. > > 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. (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.)