From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Base 64-bit Cygwin now requires Perl?
Date: Mon, 13 Jan 2014 19:35:00 -0000 [thread overview]
Message-ID: <52D43FED.4060803@users.sourceforge.net> (raw)
In-Reply-To: <20140113182252.GB7186@ednor.casa.cgf.cx>
On 2014-01-13 12:22, Christopher Faylor wrote:
> Actually, I didn't upload the 64-bit groff. This is one of the reasons
> why I had reservations about people other than the package maintainers
> uploading packages. The end result is that I'm forced to deal with
> someone else's decision. This has been the case for a few of my
> packages, uploaded during the 64-bit transition. If I had created the
> package I might have paused at the perl dependency since clearly groff
> is part of base.
There is no practical difference in packaging between your 1.21-2.i686
and 1.22.2-1.x86_64; they both include basically the same scripts, and
therefore *both* should rightly depend on perl. Probably the best
solution to avoiding the perl dep in Base is to split up groff as on
Fedora, where 13 perl scripts plus their manpages and data are in a
separate groff-perl package.
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
next prev parent reply other threads:[~2014-01-13 19:35 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) [this message]
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
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=52D43FED.4060803@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--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).