From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Base 64-bit Cygwin now requires Perl?
Date: Wed, 18 Jun 2014 20:39:00 -0000 [thread overview]
Message-ID: <87wqcevtp3.fsf@Rainer.invalid> (raw)
In-Reply-To: <53A1F336.3030509@breisch.org> (Chris J. Breisch's message of "Wed, 18 Jun 2014 16:14:46 -0400")
Chris J. Breisch writes:
> lynx depends on perl. I'm not 100% sure this is a valid dependency.
It isn't, scripts in the doc folder shouldn't trigger a dependency. On
x86 this dependency isn't there, only on x86_64 -- which indicates it is
a function of the cygport version that generated the package. But
really the setup.hint should just be changed for x86_64 (Corinna could
do that, I suppose).
> However, I wonder if the answer here isn't just to move perl into
> base. perl scripts are used everywhere, even in startup/shutdown
> scripts on some Unix systems. I think most people at this point expect
> a Unix environment to have perl.
Perl is too heavy for Base. If we can help it it shouldn't be there.
> So, yes, there are options to remove this dependency. The lynx one
> seems to me to be the easiest, but I could be wrong.
There's links as well, but I don't know if it makes a difference
feature-wise. It does not depend on perl in both architectures in any
case. If man-db uses lynx by default, then it likely is easier to just
correct the dependencies.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-06-18 20:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 17:17 Steven Penny
2013-08-15 16:56 ` Warren Young
2014-01-12 15:51 ` Steven Penny
2014-01-13 12:12 ` Corinna Vinschen
2014-01-13 12:26 ` Steven Penny
2014-01-13 17:39 ` Warren Young
2014-01-13 18:22 ` Christopher Faylor
2014-01-13 18:39 ` Christopher Faylor
2014-01-13 18:44 ` Warren Young
2014-01-13 19:35 ` Yaakov (Cygwin/X)
2014-01-13 19:21 ` Andrew Schulman
2014-01-13 19:36 ` Achim Gratz
2014-01-13 19:44 ` Andrew Schulman
2014-01-13 20:59 ` Yaakov (Cygwin/X)
2014-01-14 10:01 ` Andrew Schulman
2014-06-18 16:08 ` Steven Penny
2014-06-18 20:14 ` Chris J. Breisch
2014-06-18 20:25 ` Douglas Coup
2014-06-18 20:34 ` Larry Hall (Cygwin)
2014-06-18 20:39 ` Achim Gratz [this message]
2014-06-18 21:00 ` Corinna Vinschen
2014-10-31 16:59 ` Steven Penny
2014-10-31 19:35 ` Ken Brown
2014-10-31 19:56 ` Yaakov Selkowitz
2014-10-31 20:47 ` Ken Brown
2014-10-31 21:04 ` Corinna Vinschen
2014-10-31 21:24 ` Yaakov Selkowitz
2014-11-01 15:51 ` Corinna Vinschen
2014-11-01 16:07 ` Ken Brown
2014-11-01 17:35 ` Corinna Vinschen
2014-11-01 18:12 ` Ken Brown
2014-11-01 19:16 ` Corinna Vinschen
2014-11-02 7:34 ` Base 64-bit Cygwin now requires Perl? (indent DONE) Jari Aalto
2014-11-03 9:31 ` Corinna Vinschen
2014-10-31 19:50 ` Base 64-bit Cygwin now requires Perl? Achim Gratz
2013-08-15 20:39 Daniel Jensen
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=87wqcevtp3.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@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).