From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Runtime package dependencies and compilation order
Date: Wed, 01 Jun 2016 10:38:42 -0400 [thread overview]
Message-ID: <jwvy46pj7zh.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: CACY1KR3_D1WPPv84VurMVX8A-ZoeamuJX-8SpyeX9VuA0BN3RQ@mail.gmail.com
> From my understanding specifying package B as dependency solves such
> issues, as package manager installs B before A. So the only solution I see
> in such situation is to create package A-base, A-B (B-related functionality
> that has two packages as dependency - A-base and B) and A-C (similar to
> A-B).
Without knowing more of the details (and taking as a given that you're
not interested in extending the ELPA infrastructure to support
disjunction in dependencies), I think your solution is indeed about as
good as it gets.
There is a hackish alternative, where you provide an B-C (meta) package,
with two *versions* (one that depends on B and the other that depends on
C), but ELPA generally presumes that there's only one interesting
version (the latest), so it'll probably be cumbersome to use.
But there's no reason to take ELPA as something that's cast in stone.
So I recommend you file a bug-report asking for better support for your
use-case.
Stefan
next prev parent reply other threads:[~2016-06-01 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 9:05 Runtime package dependencies and compilation order Boris
2016-05-31 14:47 ` Michael Heerdegen
2016-06-01 14:19 ` Boris
[not found] ` <mailman.624.1464790782.1216.help-gnu-emacs@gnu.org>
2016-06-01 15:32 ` Emanuel Berg
2016-06-01 14:38 ` Stefan Monnier [this message]
[not found] <mailman.513.1464614585.1216.help-gnu-emacs@gnu.org>
2016-05-30 13:40 ` Emanuel Berg
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=jwvy46pj7zh.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.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.
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).