public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Base 64-bit Cygwin now requires Perl?
Date: Fri, 31 Oct 2014 19:56:00 -0000	[thread overview]
Message-ID: <5453E987.2080102@cygwin.com> (raw)
In-Reply-To: <5453E47D.40308@cornell.edu>

On 2014-10-31 14:35, Ken Brown wrote:
> On 10/31/2014 12:59 PM, Steven Penny wrote:
>> On Fri, Aug 9, 2013 at 12:17 PM, Steven Penny wrote:
>>> Because of this dependency line
>>
>> This issue is back again, now with
>>
>> bash
>>    _update-info-dir
>>      texinfo
>>        perl
>
> This is a side effect of the fact that I switched to cygport for
> packaging when I took over as texinfo maintainer.  cygport (correctly)
> detected perl as a dependency because texinfo provides perl scripts.  In
> fact, the most important program in texinfo is /usr/bin/makeinfo, which
> is a symlink to a perl script.
>
> I'll wait for guidance from above before doing anything about this.

Fedora splits out texinfo into 3 packages:

1) texinfo: makeinfo, texi2any, pod2texi, /usr/share/texinfo, 
/usr/share/info/texinfo*

2) info: info, infokey, install-info, /usr/share/info/info*

3) texinfo-tex: texindex, texi2dvi, texi2pdf, pdftexi2dvi, 
/usr/share/texmf*/tex/texinfo

In this setup, only 'info' would be required by _update-info-dir and 
should not have any Perl dependencies.  texinfo would be in 'Devel' and 
would have Perl dependencies, while texinfo-tex would also have texlive 
dependencies.


Yaakov


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

  reply	other threads:[~2014-10-31 19:56 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
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 [this message]
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=5453E987.2080102@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --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).