From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: midnight commander -> which screen library
Date: Tue, 10 Feb 2009 09:26:34 +0100 [thread overview]
Message-ID: <1234254394.18160.1960.camel@localhost> (raw)
In-Reply-To: <4990C41A.3090203@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
Am Dienstag, den 10.02.2009, 02:02 +0200 schrieb Petteri Räty:
> Mike Frysinger wrote:
> > On Monday 09 February 2009 13:32:24 Nikos Chantziaras wrote:
> >> Enrico Weigelt wrote:
> >>> @mc.o (*1) we're currently discussing which screen library to keep.
> >>> Either ncurses or slang will be dropped (bundled slang will anyway)
> >>> Both have their pros and cons, so we haven't decided yet.
> >>>
> >>> What do you suggest, which screen library to keep ?
> >>>
> >>> BTW: 4.6.2 is soon coming (only 1 bug left) :)
> >> unicode? ( >=sys-libs/slang-2.1.3 )
> >> !unicode? ( sys-libs/ncurses )
> >>
> >> If Unicode isn't possible with ncurses, keep slang :P No Unicode
> >> support would be... not good.
> >
> > that doesnt make any sense. both ncurses and slang work just fine with and
> > without unicode. i dont think he was asking about Gentoo anyways ... he was
> > asking about upstream mc.
> >
> > the proper string under Gentoo would be:
> > ncurses? (
> > unicode? ( sys-libs/ncurses[unicode] )
> > !unicode? ( sys-libs/ncurses )
> > )
> > !ncurses? ( slang? ( >=sys-libs/slang-2.1.3 ) )
> > -mike
> >
>
> ncurses? ( sys-libs/ncurses[unicode?] )
> !ncurses? ( slang? ( >=sys-libs/slang-2.1.3 ) )
Since you want always one of {slang,ncurses} you'll probably want
something like this:
slang? ( >=sys-libs/slang-2.1.3 )
!slang? ( sys-libs/ncurses[unicode?] )
and drop the ncurses USE-flag completely. Or set USE="+ncurses" and do
this:
ncurses? ( sys-libs/ncurses[unicode?] )
!ncurses? ( >=sys-libs/slang-2.1.3 )
... depends on what you want per default.
--
-------------------------------------------------------
Tiziano Müller
Gentoo Linux Developer, Council Member
Areas of responsibility:
Samba, PostgreSQL, CPP, Python, sysadmin
E-Mail : dev-zero@gentoo.org
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30
--
-------------------------------------------------------
Tiziano Müller
Gentoo Linux Developer, Council Member
Areas of responsibility:
Samba, PostgreSQL, CPP, Python, sysadmin
E-Mail : dev-zero@gentoo.org
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-10 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 13:42 [gentoo-dev] midnight commander -> which screen library Enrico Weigelt
2009-02-09 17:30 ` Mike Frysinger
2009-02-09 18:32 ` [gentoo-dev] " Nikos Chantziaras
2009-02-09 19:37 ` Mike Frysinger
2009-02-09 20:36 ` Nikos Chantziaras
2009-02-10 3:22 ` Mike Frysinger
2009-02-10 7:26 ` [gentoo-dev] Can't format floppy or write to it Branko Badrljica
2009-02-10 7:24 ` Josh Saddler
2009-02-10 19:43 ` Mike Frysinger
2009-02-10 0:02 ` [gentoo-dev] Re: midnight commander -> which screen library Petteri Räty
2009-02-10 3:20 ` Mike Frysinger
2009-02-10 8:26 ` Tiziano Müller [this message]
2009-02-10 19:44 ` Mike Frysinger
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=1234254394.18160.1960.camel@localhost \
--to=dev-zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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