public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] mysql 10.1.26-1
Date: Sun, 10 Sep 2017 19:16:00 -0000	[thread overview]
Message-ID: <e3685679-8c10-a88c-8eec-6cc282496e1c@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAHSx_SswX5_qWY2fKfM_yPRzYj20jSphwLKyjJbuBwoocp8c1w@mail.gmail.com>

On 2017-09-10 12:03, Wayne Davison wrote:
> On Sun, Sep 3, 2017 at 2:46 PM, Yaakov Selkowitz wrote:
>> This is an update to the latest 10.1 release:
> 
> Is there any chance that readline support is going to make a comeback
> in mysql? I downloaded the src, changed the readline option in the
> cygport file to "-DWITH_READLINE=ON" (it was "OFF") and compiled my
> own mysql.exe so that I have access to the much-superior readline
> editing (I can't stand being without Ctrl+R searching, Ctrl+_ undo,
> etc, etc), but it would be nice if it was a default part of each
> release.
> 
> Aside: it's too bad the cygport file doesn't seem to have a way to
> mention all the packages required for a build. I waded through the
> cmake output and installed all of the following (I already had things
> like gcc installed) -- hopefully this will help someone:
> 
> cmake, openssl-devel, libncurses-devel, libpcre-devel,
> libgcrypt-devel, libiconv-devel, libxml2-devel, liblzo2-devel,
> liblzma-devel, liblz4-devel, libbz2-devel, bison, libreadline-devel

Add to or define DEPEND= - note singular - for build time dependencies

https://cygwinports.github.io/cygport/check_funcs_cygpart.html#robo906

some maintainers have so many packages and dependencies installed that it may be
hard for them to figure out what each package needs; it would be great if this
info was captured as a build-depends: line in each package's setup.ini entry.

Add to or define REQUIRES= - note plural - for run time dependencies

https://cygwinports.github.io/cygport/pkg_pkg_cygpart.html#robo443

cygport tries to figure these out, and the result is captured as a requires:
line in each package's setup.ini entry.

Note that if the cygport file defines PKG_NAMES= with more than one package,

https://cygwinports.github.io/cygport/pkg_pkg_cygpart.html#robo432

then each Cygwin package should have its own <pkg>_CONTENTS=, <pkg>_DEPEND=, and
<pkg>_REQUIRES= entries in the cygport file, or sometimes in a <pkg>.list file
in the CYGWIN-PATCHES directory.

You can submit cygport file patches on the cygwin-apps list, where discussions
on building packages normally occurs.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2017-09-10 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <59ac79b9.09f7540a.8a5f.17beSMTPIN_ADDED_MISSING@mx.google.com>
2017-09-10 18:03 ` Wayne Davison
2017-09-10 19:16   ` Brian Inglis [this message]
2017-09-03 21:49 Yaakov Selkowitz

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=e3685679-8c10-a88c-8eec-6cc282496e1c@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).