unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: library dependencies and unit/integration testing
Date: Mon, 01 Mar 2010 10:59:47 -0700	[thread overview]
Message-ID: <m3sk8jhqi4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87pr3oosk6.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 01 Mar 2010 11:33:29 -0600")

>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:

Ted> What capabilities does Emacs offer for tracking library dependencies
Ted> beyond 'require and `load-history'?  I think versions (as stated by the
Ted> Version header) are not tracked and that's a basic requirement.  Then,
Ted> how would a library state it depends on "foo v.1 or later and bar v.2
Ted> exactly"?

Emacs doesn't provide much.

package.el defines an extension to the header comments for tracking
dependencies.  It looks like (example from ruby-compilation):

;;; Package-Requires: ((ruby-mode "1.0") (inf-ruby "2.0"))

This just means that this package requires ruby-mode >= 1.0 and inf-ruby
>= 2.0.

I only allowed >= requires to keep package.el simple, and because I
don't think there is any real need for anything more complicated.

Ted> In order to ensure these dependencies are tracked correctly, is there a
Ted> *standard* way in Emacs to test if a library loads and runs some basic
Ted> unit and integration tests correctly?

No.

For package.el it would be a bad idea to load all packages.  This is
slow, and loading a package can have undesirable side effects.

Tom




  reply	other threads:[~2010-03-01 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 17:33 library dependencies and unit/integration testing Ted Zlatanov
2010-03-01 17:59 ` Tom Tromey [this message]
2010-03-02 13:23   ` Ted Zlatanov
2010-03-02 15:25     ` Jonas Bernoulli
2010-03-02 15:47       ` Ted Zlatanov

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=m3sk8jhqi4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).