all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Alexandrov <dag@gnui.org>
To: Thomas Schneider <qsx@chaotikum.eu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: use-package, package.el, and system packages cooperation
Date: Mon, 27 Jul 2020 01:50:56 +0300	[thread overview]
Message-ID: <eeoxq4a7.dag@gnui.org> (raw)
In-Reply-To: <931B677D-3813-435D-802C-E1207856CBBD@chaotikum.eu> (Thomas Schneider's message of "Sun, 26 Jul 2020 20:23:08 +0200")

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

Thomas Schneider <qsx@chaotikum.eu> wrote:
> I want:
> - to install packages via the system package manager as much as possible

If you drop that wish, things will became much easier.

>   This is especially important for packages such as pdf-tools, which require development headers of several libraries, but are readily installed via system packages

pdf-tools are not released often, so the chances to get hit by version mismatch with pdf-tools-server is quite low.

> - to continue using use-package, or something else that helps me structure my init.el

Hm...  The last time I looked at use-package I found out, that this is a tool that prevents me from structuring my .emacs.d.  Never mind though, this is orthogonal to your question.

> - not to download half of MELPA the first time I start Emacs on a new host

Then check the packages in your VCS along with your own code.

>   Yes, this contradicts the (setq use-package-always-ensure t) in my init.el, because otherwise … stuff broke.  I don’t remember the details why.

Because packages are absent and your .emacs.d hard require them? ;-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-07-26 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 18:23 use-package, package.el, and system packages cooperation Thomas Schneider
2020-07-26 22:50 ` Dmitry Alexandrov [this message]
2020-07-27  8:18   ` tomas
2020-08-02 10:54 ` akater

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eeoxq4a7.dag@gnui.org \
    --to=dag@gnui.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=qsx@chaotikum.eu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.