Philip Kaludercic writes: > Joseph Turner writes: > >> Philip Kaludercic writes: >> >>> Joseph Turner writes: >>> >>>> Philip Kaludercic writes: >>>> >>>>> Joseph Turner writes: >> We also might want to add another option for >> package-vc-allow-side-effects like 'user-defined, which only runs :make >> and :shell-command args which were specified by the user (as opposed to >> those which were downloaded from elpa). WDYT? > > That sounds like a good idea, but let us do that in a separate patch. Okay! >> To update the manual, shall I edit doc/emacs/package.texi directly or is >> there another file to edit? > > Yes, just update the table under the "Specifying Package Sources" subsection. See patch. >>> If :shell-command fails, do we really want to proceed to :make? >> >> Up to you! I was following the lead of elpa-admin.el. > > In that case let us do that too, unless there is a good reason not to. +1 >> I switched the first two cases. I think pcase is readable here, >> especially if we add an 'user-defined option. What would you use >> instead? > > I would have just used a regular cond. > > --8<---------------cut here---------------start------------->8--- > (cond > ((null package-vc-process-make) > ...) > ((listp package-vc-process-make) > ...) > (...)) > --8<---------------cut here---------------end--------------->8--- > > But this doesn't matter, do what you prefer. Thank you! I like pcase here. >> +Be careful when changing this option as processing :make and >> +:shell-command will run potentially harmful code. > > Sounds scary. I guess that is the point, but what do you think about > something like > > Be careful when changing this option, as installing and updating a > package can potentially run harmful code. If possible, allow packages > you trust to run code, if it is necessary for a package to be properly > initialised. Thank you! What do you think about the version in the attached patch? >> +When set to a list of symbols (packages), run commands for only >> +packages in the list. When `nil', never run commands. Otherwise >> +when non-`nil', run commands for any package with :make or >> +:shell-command specified. > > Watch out. According to (elisp) Documentation Tips, nil is not quoted. Good to know! Fixed.