Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.29-rc2
Date: Thu, 20 Oct 2016 19:08:58 +0200	[thread overview]
Message-ID: <201610201908.58407.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20161020164016.olhnllmvwixbvzc4@ws.net.home>

On Thursday 20 October 2016, Karel Zak wrote:
> On Thu, Oct 20, 2016 at 06:28:05PM +0200, Ruediger Meier wrote:
> > We don't need to handle such broken installation. In drone.io
> > script you could try
> >   apt-get install -qq libncursesw5-dev
>
> We call travis-functions.sh from drone.io, something like:
>
> diff --git a/.travis-functions.sh b/.travis-functions.sh
> index 6fcf019..3766534 100755
> --- a/.travis-functions.sh
> +++ b/.travis-functions.sh
> @@ -95,6 +95,14 @@ function travis_install_script
>  		libsystemd-daemon-dev \
>  		libsystemd-journal-dev \
>
>  		|| true
>
> +
> +	# install only if available
> +	sudo apt-get install -qq >/dev/null \
> +		libncursesw6-dev \
> +		|| sudo apt-get install -qq >/dev/null \
> +			libncursesw5-dev \
> +			|| true
> +
>  }
>
>  function osx_install_script
>
>
> .. I guess we prefer ncurses6. Or it's too crazy? :-)

Just checked, v6 is even not available on the newer Ubuntu Trusty which 
we have on travis. But we are using v6 on OSX already :)

Maybe this would be enough for now

diff --git a/.travis-functions.sh b/.travis-functions.sh
index 6fcf019..3766534 100755
--- a/.travis-functions.sh
+++ b/.travis-functions.sh
@@ -95,6 +95,14 @@ function travis_install_script
 		libsystemd-daemon-dev \
 		libsystemd-journal-dev \
+		libncursesw5-dev \
 		|| true
 }


BTW I find the older libs usually more useful on test systems. Because 
the newer ones are tested already on the developer systems and by 
distro packagers ;)

cu,
Rudi

  reply	other threads:[~2016-10-20 17:09 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 [this message]
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
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=201610201908.58407.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=kzak@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox