public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ingmar Vanhassel <ingmar.stdin@gmail.com>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: New eclass: cmake-utils.eclass
Date: Fri, 09 Nov 2007 03:46:15 +0100	[thread overview]
Message-ID: <1194576034-sup-8763@indigo> (raw)
In-Reply-To: <47339BAF.30409@necoro.eu>

Excerpts from René 'Necoro' Neumann's message of Fri Nov 09 00:28:47 +0100 2007:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Steve Long schrieb:
> > René 'Necoro' Neumann wrote:
> >> cmake-utils_src_enable python => -DENABLE_python=...
> >>
> >> Wanted would be that it returned -DENABLE_PYTHON=...
> >>
> >> I'm not into bash scripting that much, so I do not know a way to do so -
> >> but I guess someone else is ;)
> >>
> > Unfortunately BASH doesn't support ksh93 or zsh style casting to uppercase.
> > The best way really is via tr:
> > alias toUpper='tr [[:lower:]] [[:upper:]]'
> > alias toLower='tr [[:upper:]] [[:lower:]]'
> > 
> > (er aliases don't normally work in scripts, but you get the idea.) Bear in
> > mind that tr reads stdin and writes to stdout. It has the advantage of
> > being locale-safe. Every other method I've looked at is much slower and
> > only works with ASCII.
> > 
> > A function wouldn't be too hard:
> > toUpper() {
> >         for i; do
> >         echo "$i" |tr [[:lower:]] [[:upper:]]
> >         done
> > }
> > 
> > Usage depends on the parameters you pass.
> > var=$(toUpper $var) # for single vars with no newlines in
> 
> This is right the version I've chosen ... so with the help of Steve: a
> small patch ;)
> 
> Regards,
> Necoro
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD4DBQFHM5uv4UOg/zhYFuARAuELAJjnlDCFDMm3e2mJqYuyT4nkFoaaAJ4go9qp
> Qca9r8Y7LpD0YSSylUh2BQ==
> =517n
> -----END PGP SIGNATURE-----

Hi Necoro,

It looks like you want to use

'cmake-utils_use_enable python PYTHON'

It's mentioned in the cmake-utils.eclass manpage (app-portage/eclass-manpages),
as well as in the patch you just sent: cmake-utils_use_enable <USE flag> [flag name]

:-)

Regards,
Ingmar Vanhassel

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-12-28  1:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09 19:15 [gentoo-dev] New eclass: cmake-utils.eclass Wulf C. Krueger
2007-09-09 19:48 ` Piotr Jaroszyński
2007-09-09 20:32   ` Mike Frysinger
2007-09-09 20:11 ` [gentoo-dev] " Christian Faulhammer
2007-09-09 20:44 ` [gentoo-dev] " Mike Frysinger
2007-09-09 21:05   ` Wulf C. Krueger
2007-09-09 21:03 ` [gentoo-dev] " Christian Faulhammer
2007-09-10  8:00 ` [gentoo-dev] " Luca Barbato
2007-09-10 11:08 ` Thomas Anderson
2007-11-02 22:33 ` Wulf C. Krueger
2007-11-08 16:20 ` René 'Necoro' Neumann
2007-11-08 22:57   ` [gentoo-dev] " Steve Long
2007-11-08 23:28     ` René 'Necoro' Neumann
2007-11-09  2:46       ` Ingmar Vanhassel [this message]
2007-11-09  3:04       ` Ingmar Vanhassel
2007-11-09  9:10         ` René 'Necoro' Neumann
2007-11-09 15:58           ` Wulf C. Krueger
2007-11-09 16:10             ` René 'Necoro' Neumann
2007-11-09 17:45               ` Marijn Schouten (hkBst)
2007-11-09 17:51                 ` Marijn Schouten (hkBst)

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=1194576034-sup-8763@indigo \
    --to=ingmar.stdin@gmail.com \
    --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