From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Runtime package dependencies and compilation order
Date: Mon, 30 May 2016 15:40:17 +0200 [thread overview]
Message-ID: <86twhffyv2.fsf@student.uu.se> (raw)
In-Reply-To: mailman.513.1464614585.1216.help-gnu-emacs@gnu.org
Boris <d12frosted@gmail.com> writes:
> Recently I've faced following problem. I have
> a package A that might depend on package B or
> (disjunction) package C. But dependency list
> is not known upwards, because the list itself
> depends on user settings. So I don't specify
> B and C in package requires section of
> package A.
"package B or (disjunction) package C" - does
this mean you can't `require' both?
Why not? Collisions?
If so, the idea of the "require list as an
option" strikes me as odd.
Did you see it all over the MELPA world? Scary.
Better: require both B and C.
If you don't want to change the code all over
the place in A (which also is possible), there
are many workarounds that shouldn't be too
slow, for example can you create a "function
pool" and a bunch of variables in A to hold
functions. When the user switches from B to
C mode, or the other way around, the function
pool reassigns the functions in effect in A.
--
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
- so far: 42 Blogomatic articles -
next parent reply other threads:[~2016-05-30 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.513.1464614585.1216.help-gnu-emacs@gnu.org>
2016-05-30 13:40 ` Emanuel Berg [this message]
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
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=86twhffyv2.fsf@student.uu.se \
--to=embe8573@student.uu.se \
--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).