[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#15108: closed (24.3.50; Package dependency documen

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#15108: closed (24.3.50; Package dependency documentation)
Date: Sun, 15 Dec 2013 01:09:01 +0000

Your message dated Sat, 14 Dec 2013 20:08:32 -0500
with message-id <address@hidden>
and subject line Re: bug#15108: [Patch] Updated package dependencies
has caused the debbugs.gnu.org bug report #15108,
regarding 24.3.50; Package dependency documentation
to be marked as done.

(If you believe you have received this mail in error, please contact

15108: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15108
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3.50; Package dependency documentation Date: Fri, 16 Aug 2013 02:23:07 +0200
I noticed that the "Packaging Basics" section in the Emacs Lisp manual
suggests that version numbers in `Package-Requires' headers are
optional, however the explanation of `Package-Requires' makes it clear
that the version specifier is necessary and testing confirms this.

The values `foo', `(foo)' and `((foo))' all cause an error to be
signaled by `package-buffer-info'. This seems to me that there is no
"possibly" about it.

It's only a tiny change and I hope it's OK. I have tried to follow the
guidelines found in the Emacs manual about sending patches, I didn't
find any reference about diffs of multiple files, so I hope it's OK to
send the diffs separately.

Attachment: ChangeLog.diff
Description: ChangeLog diff

Attachment: package.diff
Description: package.texi diff

--- End Message ---
--- Begin Message --- Subject: Re: bug#15108: [Patch] Updated package dependencies Date: Sat, 14 Dec 2013 20:08:32 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
> Taken care of in attached patch. I was unsure of how to deal with these
> situations, so I explicitly signal a (hopefully) clear error. Just
> letting it crash on trying to get the cdr of a symbol seemed messy.
> Please let me know what you think.

Thanks, installed in trunk with a few changes,


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]