From: Mark Oteiza <mvoteiza@udel.edu>
To: Tim Cross <theophilusx@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Package.el and specifying alternative dependencies
Date: Sat, 04 Mar 2017 16:57:12 -0500 [thread overview]
Message-ID: <87lgskogcn.fsf@holos> (raw)
In-Reply-To: <CAC=50j9eim9fro4wWB2i46WckdhGDGWS22ccosSJMmA04hW_8w@mail.gmail.com> (Tim Cross's message of "Fri, 3 Mar 2017 11:41:23 +1100")
Tim Cross <theophilusx@gmail.com> writes:
> Is there a way to specify alternative dependencies in a package?
>
> Situation: installing a package is resulting in an additional package being installed
> even though the dependencies for the package have already been satisfied by another
> package. This results in two packages being installed which provide overlapping
> functionality.
>
> Example. I have installed org-plus-contrib. I then install elfeed-org, which has a
> dependency on org. This results in the org package being installed, but org is
> already installed as part of the org-plus-contrib package.
>
> I'm trying to work out if this is a problem with how dependencies are defined in the
> elfeed-org package or is it a problem with how org-plus-conrib is specifying what
> dependency it satisfies? Need to know in order to determine where this issue needs to
> be logged.
IIUC, package.el figures out dependencies by package name, not by the
features it provides. So, I think the answer to your question is no.
next prev parent reply other threads:[~2017-03-04 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 0:41 Package.el and specifying alternative dependencies Tim Cross
2017-03-04 21:57 ` Mark Oteiza [this message]
2017-03-04 22:32 ` Tim Cross
2017-03-04 22:46 ` Kaushal Modi
2017-03-04 23:44 ` Tim Cross
2017-04-11 22:37 ` Kaushal Modi
2017-04-12 7:35 ` Tim Cross
2017-04-12 7:44 ` Thien-Thi Nguyen
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=87lgskogcn.fsf@holos \
--to=mvoteiza@udel.edu \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@gmail.com \
/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.