public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] Inetutils 1.9.4
Date: Mon, 08 Feb 2016 19:16:00 -0000	[thread overview]
Message-ID: <871t8nypve.fsf@Rainer.invalid> (raw)
In-Reply-To: <20160208140438.GJ27646@calimero.vinschen.de> (Corinna Vinschen's	message of "Mon, 8 Feb 2016 15:04:38 +0100")

Corinna Vinschen writes:
>> So I added these on the 'required' lines.
>
> They are not actually *required* to run inetd, right?  Does it really
> make sense to add them as require packages then?

I don't think so (not checked all scripts, though), although people who
expect these programs to become available with inetutils might say
otherwise.  I would tend to omit those in order to keep the dependencies
down.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

  reply	other threads:[~2016-02-08 19:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 18:01 D. Boland
2016-02-08 14:04 ` Corinna Vinschen
2016-02-08 19:16   ` Achim Gratz [this message]
2016-02-13  6:59   ` D. Boland
2016-02-13 17:16     ` Corinna Vinschen
2016-02-16 16:31       ` D. Boland
2016-02-16 18:34         ` Achim Gratz
2016-02-16 19:26           ` Daniel Boland
2016-02-17 17:33         ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2015-10-31 10:33 D. Boland
2015-10-31 12:29 ` Marco Atzeri
2015-10-31 23:04   ` D. Boland
2015-11-01  8:01     ` Marco Atzeri
2015-11-01 14:21       ` D. Boland
2015-11-01 14:45         ` Marco Atzeri
2015-11-02  7:04           ` D. Boland
2015-11-02  9:56             ` Corinna Vinschen
2015-11-02  9:58               ` Corinna Vinschen
2015-11-02 14:44                 ` Corinna Vinschen
2015-12-30  7:55                   ` D. Boland
2016-01-07 10:35                     ` Corinna Vinschen

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=871t8nypve.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).