From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Tom Tromey <tromey@redhat.com>
Cc: Nic Ferrier <nferrier@ferrier.me.uk>, emacs-devel@gnu.org
Subject: Re: package.el can't install a circular depend and it should be able to.
Date: Mon, 14 Jan 2013 21:14:11 -0500 [thread overview]
Message-ID: <jwvbocrp52h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <877gnfmo83.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 14 Jan 2013 14:47:08 -0700")
Tom> It was intended to do a topological sort of the graph and activate
Tom> packages from the bottom up. If this isn't working then there is a bug.
Stefan> Do we actually need such a topological sort? I mean the only
Stefan> place where ordering might matter is when loading the autoloads
Stefan> file, AFAICT (for all other steps like download, unpack, compile
Stefan> the order in which packages are processed doesn't matter).
> I thought byte-compiling one package could require that package's
> dependencies, say via eval-when-compile.
Sure, but we can download, unpack, and activate all the packages first,
and only then byte-compile them (at which point, `require' and
eval-when-compile will work just fine, because the other packages are
activated, even if not yet byte-compiled).
Stefan
prev parent reply other threads:[~2013-01-15 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 0:24 package.el can't install a circular depend and it should be able to Nic Ferrier
2013-01-04 14:26 ` Tom Tromey
2013-01-04 17:15 ` Stephen J. Turnbull
2013-01-11 23:27 ` Stefan Monnier
2013-01-12 2:43 ` Stefan Monnier
2013-01-12 14:14 ` Nic Ferrier
2013-01-12 15:03 ` Stefan Monnier
2013-01-12 16:27 ` Nic Ferrier
2013-01-13 0:02 ` Stefan Monnier
2013-01-14 21:47 ` Tom Tromey
2013-01-15 0:00 ` Xue Fuqiao
2013-01-15 1:24 ` Stephen J. Turnbull
2013-01-15 2:14 ` Stefan Monnier [this message]
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=jwvbocrp52h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=nferrier@ferrier.me.uk \
--cc=tromey@redhat.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.