public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [RFU 1.7] {emacs,emacs-X11,emacs-el}-23.0.92-10
Date: Thu, 18 Jun 2009 20:09:00 -0000	[thread overview]
Message-ID: <4A3A9EEF.6010703@cornell.edu> (raw)
In-Reply-To: <20090618021023.GA3683@ednor.casa.cgf.cx>

On 6/17/2009 10:10 PM, Christopher Faylor wrote:
> On Wed, Jun 17, 2009 at 07:22:33PM -0600, Eric Blake wrote:
>> According to Ken Brown on 6/17/2009 7:07 PM:
>>> On 6/17/2009 6:22 PM, Jon TURNEY wrote:
>>>> Sorry for not mentioning this before you did the packaging, but can I
>>>> suggest that emacs-X11 package setup.hint should have font-adobe-dpi75
>>>> and font-misc-misc added to the requires: line
>>> Good idea.  Can someone just do that now, or does it have to wait for
>>> the next update?
>> I've done it for now; but you'll have to remember to update your
>> setup.hint for the next update.
> 
> Thanks for doing this Eric.

Thanks from me too, Eric.  I noticed that you also added cygwin to the 
requires: line of emacs-X11, even though emacs-X11 requires emacs which 
requires cygwin.  Is this just a precaution in case setup.exe messes up 
the dependencies, or is there some deeper reason?

(BTW, I see that you also added cygwin to emacs-el, but it isn't 
actually needed.  In fact, I'm just realizing that emacs-el doesn't even 
need to require emacs.)

Ken

  reply	other threads:[~2009-06-18 20:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 15:43 Ken Brown
2009-06-12  9:24 ` Corinna Vinschen
2009-06-17 22:22 ` Jon TURNEY
2009-06-18  1:07   ` Ken Brown
2009-06-18  1:22     ` Eric Blake
2009-06-18  2:10       ` Christopher Faylor
2009-06-18 20:09         ` Ken Brown [this message]
2009-06-19  1:49           ` Eric Blake
2009-06-19  5:33             ` Christopher Faylor
2009-06-19 20:20               ` Ken Brown
2014-04-25 14:31   ` emacs-X11 font dependencies Jon TURNEY
2014-04-25 20:16     ` Ken Brown

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=4A3A9EEF.6010703@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-apps@cygwin.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.
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).