From: Philip Kaludercic <philipk@posteo.net>
To: Hugo Thunnissen <devel@hugot.nl>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [ELPA] New Package: phpinspect.el
Date: Tue, 15 Aug 2023 21:56:13 +0000 [thread overview]
Message-ID: <874jl0j7gi.fsf@posteo.net> (raw)
In-Reply-To: <020fb83b-8d62-460b-5673-c2b6e71345de@hugot.nl> (Hugo Thunnissen's message of "Tue, 15 Aug 2023 23:33:03 +0200")
Hugo Thunnissen <devel@hugot.nl> writes:
> On 8/15/23 22:28, Philip Kaludercic wrote:
>>
>> I am not familiar with Cask, what does this provide over a simple
>> Makefile?
>
>
> It locally installs the package's dependencies and starts emacs with a
> clean profile that only has those dependencies available. It doesn't
> do much, but it's easy to use and it seems to help prevent "it works
> with my setup" scenarios. I only started using it recently though so
> I'm not very familiar with it, nor am I very skilled with make for
> that matter ;)
>
> What would a simple Makefile for a typical elisp package look like? Is
> it common practice to create clean environments like cask does?
This article goes into it https://nullprogram.com/blog/2020/01/22/,
though I understand now that it doesn't do the same thing (or at least
you would have to manually implement something like creating a clean
environment or installing dependencies).
next prev parent reply other threads:[~2023-08-15 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 20:22 [ELPA] New Package: phpinspect.el Hugo Thunnissen
2023-08-12 4:56 ` Stefan Monnier
2023-08-12 5:04 ` Stefan Monnier
2023-08-15 17:45 ` Hugo Thunnissen
2023-08-15 20:28 ` Philip Kaludercic
2023-08-15 21:33 ` Hugo Thunnissen
2023-08-15 21:56 ` Philip Kaludercic [this message]
2023-08-15 22:03 ` Stefan Monnier
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=874jl0j7gi.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=devel@hugot.nl \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).