public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libucl/
Date: Sat,  6 May 2017 15:21:22 +0000 (UTC)	[thread overview]
Message-ID: <1494084011.b071e217316205e7e189e6f903b59dc594c66080.mjo@gentoo> (raw)

commit:     b071e217316205e7e189e6f903b59dc594c66080
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sat May  6 15:19:51 2017 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sat May  6 15:20:11 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b071e217

dev-libs/libucl: update flag description for USE=utils.

The "utils" USE flag enables two utilities currently: chargen and
objdump. I've mentioned them explicitly in metadata.xml, and left
a comment about a new utility in a future (unpackaged) version.

Gentoo-Bug: 600762

Package-Manager: Portage-2.3.3, Repoman-2.3.1

 dev-libs/libucl/metadata.xml | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/dev-libs/libucl/metadata.xml b/dev-libs/libucl/metadata.xml
index f564bfde4e3..6d4d014359b 100644
--- a/dev-libs/libucl/metadata.xml
+++ b/dev-libs/libucl/metadata.xml
@@ -2,16 +2,20 @@
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
   <!-- maintainer-needed -->
-  <longdescription>UCL is heavily infused by nginx configuration as the example
-    of a convenient configuration system. However, UCL is fully compatible with
-    JSON format and is able to parse json files. It can also emit UCL objects
-    into different formats such as "nginx like", json, yaml and
-    compact json</longdescription>
+  <longdescription>
+    UCL is heavily infused by nginx configuration as the example of a
+    convenient configuration system. However, UCL is fully compatible
+    with JSON format and is able to parse json files. It can also emit
+    UCL objects into different formats such as "nginx like", json,
+    yaml and compact json
+  </longdescription>
   <use>
     <flag name="regex">Enable regex checking for schema</flag>
     <flag name="signatures">Enable signatures check</flag>
     <flag name="urlfetch">Enable URLs fetch</flag>
-    <flag name="utils">Builds and installs utils</flag>
+
+    <!-- in v0.8.0, also the ucl-tool utility -->
+    <flag name="utils">Install the chargen and objdump utilities</flag>
   </use>
   <upstream>
     <remote-id type="github">vstakhov/libucl</remote-id>


             reply	other threads:[~2017-05-06 15:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 15:21 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-25 17:56 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libucl/ Arthur Zamarin
2024-02-23 18:52 Arthur Zamarin
2022-10-24 15:52 Sam James
2021-03-26 19:46 Conrad Kostecki
2020-12-27 17:53 Sam James
2020-10-02  6:43 Joonas Niilola
2020-06-15  2:29 Aaron Bauman
2020-06-06  2:00 Aaron Bauman
2016-11-03 16:19 Göktürk Yüksek
2016-02-05  8:19 Patrice Clement

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=1494084011.b071e217316205e7e189e6f903b59dc594c66080.mjo@gentoo \
    --to=mjo@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