From: Philip Kaludercic <philipk@posteo.net>
To: Mohammed Sadiq <sadiq@sadiqpk.org>
Cc: 60923@debbugs.gnu.org
Subject: bug#60923: 29.0.60; package-vc-install: Allow specifying directories
Date: Tue, 14 Feb 2023 15:59:49 +0000 [thread overview]
Message-ID: <87ttzo44qy.fsf@posteo.net> (raw)
In-Reply-To: <159754a18c3ef265ad752a3dcb7e2275@sadiqpk.org> (Mohammed Sadiq's message of "Tue, 14 Feb 2023 20:58:14 +0530")
Mohammed Sadiq <sadiq@sadiqpk.org> writes:
> On 2023-02-14 01:29, Philip Kaludercic wrote:
>
>> What does "ignore" mean in this context?
>
> Ignore as in, the file is never kept in the installation directory.
I am afraid that would be contrary to the point of package-vc. The
intention is to provide the facilities to manage a package (activate,
load, update, etc.) directory from source.
But perhaps I am misunderstanding you. What would be the point of
removing the files from the installation directory?
>> package.el already supports ignoring the contents of a .elpaignore
>> file,
>> but all that does is remove a few files from the byte-compilation
>> process.
>
> I tried installing pareedit, and it doesn't seem to work. I tried:
> emacs --batch --eval='(package-vc-install
> "https://github.com/emacsmirror/paredit.git")'
(Is there a reason you specified a URL instead of the package?)
> The project contains .elpaignore, which specifies the file test.el,
> but the file test.el is still compiled to test.elc.
It seems like this is a bug in `byte-recompile-directory' or rather in
the way it is invoked from package-compile. I will have to look into
this at some point, if it is even regarded as a bug -- there was a
discussion that it is OK to attempt compiling every file in a project,
even if the actual Lisp files are only located in a subdirectory. Most
of the time the issues in test files are just due to negligence, and
could also be fixed upstream.
> Also, since
> it is installed, I'm able to access functions like
> `paredit-test-failed'.
Just like that or after loading the file?
> Or am I missing something obvious?
Nothing obvious enough for me to see.
--
Philip Kaludercic
next prev parent reply other threads:[~2023-02-14 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 4:24 bug#60923: 29.0.60; package-vc-install: Allow specifying directories Mohammed Sadiq
2023-02-13 19:59 ` Philip Kaludercic
2023-02-14 15:28 ` Mohammed Sadiq
2023-02-14 15:59 ` Philip Kaludercic [this message]
2023-02-23 13:17 ` Philip Kaludercic
2023-03-01 5:03 ` Mohammed Sadiq
2023-03-01 14:03 ` Philip Kaludercic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttzo44qy.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=60923@debbugs.gnu.org \
--cc=sadiq@sadiqpk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).