all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Tom Willemse <tom@ryuslash.org>, 15108@debbugs.gnu.org
Subject: bug#15108: [Patch] Updated package dependencies
Date: Wed, 11 Dec 2013 12:52:10 -0800 (PST)	[thread overview]
Message-ID: <9e976905-41bb-428c-afe3-ef2cf0673aa7@default> (raw)
In-Reply-To: <m3lhzrgmgp.fsf@ryuslash.org>

> I've tested it most recently bzr trunk revision 115470. All the ways to
> specify dependencies work as described before:
> 
> ;; Package-Requires: foo
> ;; Package-Requires: (foo bar)
> ;; Package-Requires: (foo (baz "1.1.0") bar)
> ;; Package-Requires: (baz "1.1.0")

Those are not all of the ways.  Most of my libraries use this way:

;; Package-Requires: ()

And most of the others (of mine) use this way (perhaps covered by
your 3rd, perhaps not, depending on your spec):

;; Package-Requires: ((fit-frame "0"))

See also bug #14941 (still unanswered, so far).





  reply	other threads:[~2013-12-11 20:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  0:23 bug#15108: 24.3.50; Package dependency documentation Tom Willemse
2013-08-16  3:46 ` Stefan Monnier
2013-08-16  6:57   ` Drew Adams
2013-08-16  7:35     ` Tom Willemse
2013-08-16  7:46       ` Drew Adams
2013-08-16  8:06         ` Tom Willemse
2013-08-16 20:58 ` bug#15108: More flexible package dependency specification Tom Willemse
2013-12-11 20:29 ` bug#15108: [Patch] Updated package dependencies Tom Willemse
2013-12-11 20:52   ` Drew Adams [this message]
2013-12-11 21:24     ` bug#15108: " Tom Willemse
2013-12-11 21:57       ` Drew Adams
2013-12-11 22:52         ` bug#15108: [Patch] Updated package dependencies, again Tom Willemse
2013-12-12 18:30   ` bug#15108: [Patch] Updated package dependencies Stefan Monnier
2013-12-12 19:23     ` Tom Willemse
2013-12-15  1:08       ` 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

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

  git send-email \
    --in-reply-to=9e976905-41bb-428c-afe3-ef2cf0673aa7@default \
    --to=drew.adams@oracle.com \
    --cc=15108@debbugs.gnu.org \
    --cc=tom@ryuslash.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. 
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.