From: "José María Alonso" <nimiux@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/lisp:master commit in: eclass/
Date: Sat, 28 Oct 2017 14:29:07 +0000 (UTC) [thread overview]
Message-ID: <1509200940.9f2b33191158b517d3aea3de953b4610d8add860.nimiux@gentoo> (raw)
commit: 9f2b33191158b517d3aea3de953b4610d8add860
Author: Chema Alonso Josa <nimiux <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 28 14:29:00 2017 +0000
Commit: José María Alonso <nimiux <AT> gentoo <DOT> org>
CommitDate: Sat Oct 28 14:29:00 2017 +0000
URL: https://gitweb.gentoo.org/proj/lisp.git/commit/?id=9f2b3319
glo-utils.eclass: Drop obsolete eclass
eclass/glo-utils.eclass | 45 ---------------------------------------------
1 file changed, 45 deletions(-)
diff --git a/eclass/glo-utils.eclass b/eclass/glo-utils.eclass
deleted file mode 100644
index dd7dab8f..00000000
--- a/eclass/glo-utils.eclass
+++ /dev/null
@@ -1,45 +0,0 @@
-# Copyright 1999-2010 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Header: $
-#
-# This eclass contains various utilities used in the Gentoo Lisp overlay
-#
-# Public functions:
-#
-# glo_usev flagname [<if_yes> [<if_no>]]
-# If $(use FLAGNAME) return true, echo IF_YES to standard output,
-# otherwise echo IF_NO. IF_YES defaults to FLAGNAME if not specified
-#
-# glo_best_flag flag+
-# Echo to stdout the first active USE flag among those supplied as parameters.
-# If none are active, echo the first one
-#
-
-glo_usev() {
- if [[ $# < 1 || $# > 3 ]]; then
- echo "Usage: ${0} flag [if_yes [if_no]]"
- die "${0}: wrong number of arguments: $#"
- fi
- local if_yes="${2:-${1}}" if_no="${3}"
- if useq ${1} ; then
- printf "%s" "${if_yes}"
- return 0
- else
- printf "%s" "${if_no}"
- return 1
- fi
-}
-
-glo_best_flag() {
- if [[ $# < 1 ]]; then
- echo "Usage: ${0} flag+"
- die "${0}: wrong number of arguments: $#"
- fi
- for flag in $@ ; do
- if use ${flag} ; then
- echo ${flag}
- return
- fi
- done
- echo ${1}
-}
next reply other threads:[~2017-10-28 14:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 14:29 José María Alonso [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-16 18:19 [gentoo-commits] proj/lisp:master commit in: eclass/ Ulrich Müller
2023-06-16 10:42 Ulrich Müller
2022-04-03 17:56 Ulrich Müller
2022-04-01 11:12 Ulrich Müller
2022-03-26 17:29 Ulrich Müller
2022-03-24 6:54 Ulrich Müller
2022-03-13 20:27 Ulrich Müller
2022-03-13 20:21 Ulrich Müller
2020-02-11 21:25 Ulrich Müller
2019-08-08 21:24 Ulrich Müller
2019-08-08 21:24 Ulrich Müller
2018-06-21 14:40 José María Alonso
2018-05-31 16:10 José María Alonso
2018-05-31 16:08 José María Alonso
2018-05-19 14:01 José María Alonso
2018-05-18 19:56 José María Alonso
2018-03-17 21:30 José María Alonso
2017-12-10 19:56 José María Alonso
2017-10-28 14:27 José María Alonso
2017-10-28 14:25 José María Alonso
2017-10-06 21:21 José María Alonso
2017-08-29 15:23 José María Alonso
2017-08-22 21:36 José María Alonso
2017-08-22 21:33 José María Alonso
2017-08-22 21:32 José María Alonso
2017-08-22 21:28 José María Alonso
2016-11-30 14:25 José María Alonso
2016-11-29 22:43 José María Alonso
2016-06-17 16:01 José María Alonso
2015-08-18 21:24 José María Alonso
2013-04-04 19:10 Stelian Ionescu
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=1509200940.9f2b33191158b517d3aea3de953b4610d8add860.nimiux@gentoo \
--to=nimiux@gentoo.org \
--cc=gentoo-commits@lists.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