All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Karel Zak <kzak@redhat.com>
Cc: Ruediger Meier <sweet_f_a@gmx.de>, util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.29-rc2
Date: Sat, 10 Dec 2016 12:15:10 -0500	[thread overview]
Message-ID: <20161210171510.GH10558@vapier.lan> (raw)
In-Reply-To: <20161020151948.3y47rv5lwmqppubf@ws.net.home>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

On 20 Oct 2016 17:19, Karel Zak wrote:
> On Thu, Oct 20, 2016 at 01:34:24PM +0200, Ruediger Meier wrote:
> > For me it looks like the even the ncurses authors do not like their own 
> > pc files. Disabled by default and it's a pain to get them built with 
> > correct names and installed in the right location. Even --prefix does 
> > not work for their pc files. Plus the backward compatibility 
> > problem ... 
> 
> OK, I have applied:
>    https://github.com/karelzak/util-linux/commit/e5cc93b5a8854fce80537f86a244977df212dcb5
> 
> with ncurses-config and fallback to old good AC_CHECK_LIB. 
> 
> We can add fallback to pkg-config too, but it sounds like overkill if
> ncurses-config is everywhere.

ugh, this change makes things worse.  the point of using pkg-config
is also to get sane cross-compiling.  by always running `xxx-config`,
it now breaks cross-compiling.

why can't we just tell distros to fix their ncurses install ?  it's
not like 2.29, released a month ago, is getting rolled out to old
distros where people can't update their ncurses systems.

"it's hard" is a pretty weak argument for distro maintainers.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-12-10 17:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 13:25 [ANNOUNCE] util-linux v2.29-rc2 Karel Zak
2016-10-20  6:03 ` Ruediger Meier
2016-10-20  9:17   ` Karel Zak
2016-10-20 10:25     ` Ruediger Meier
2016-10-20 11:00       ` Karel Zak
2016-10-20 11:34         ` Ruediger Meier
2016-10-20 15:19           ` Karel Zak
2016-10-20 16:28             ` Ruediger Meier
2016-10-20 16:40               ` Karel Zak
2016-10-20 17:08                 ` Ruediger Meier
2016-10-21 14:44                   ` Karel Zak
2016-10-21 15:03                     ` Ruediger Meier
2016-10-20 19:20             ` Ruediger Meier
2016-12-10 17:15             ` Mike Frysinger [this message]
2016-12-12 10:29               ` Karel Zak
2016-12-12 14:31                 ` Ruediger Meier
2016-12-12 14:01               ` Ruediger Meier
2016-12-12 14:28                 ` Karel Zak
2016-12-12 18:27                   ` Mike Frysinger
2016-12-13 11:44                     ` Karel Zak
2016-12-12 17:52                 ` Mike Frysinger
2016-10-20 17:11 ` Ruediger Meier

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=20161210171510.GH10558@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=kzak@redhat.com \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.