public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings
Date: Sun, 10 Aug 2014 15:22:11 +0300	[thread overview]
Message-ID: <20140810152211.2cc5ae94@sf> (raw)

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

Hello World!

TL;DR:
  This evening I plan to mangle ~3000 ebuilds in the main tree
  by dropping trailing '.' in all 'DESCRIPTION=' fields (except "etc." case)

Long story:

As you may know newest portage release 2.2.11
got a minor (but chatty) QA warning:
    DESCRIPTION ends with a '.' character

    https://github.com/gentoo/portage/commit/06637c4215d55c57517739214c6e0fd6f8f53914
    https://bugs.gentoo.org/438976

About ~3000 ebuilds are affected, thus I've sketched a mangling script:

    https://github.com/trofi/gentoo-qa/blob/master/check_description.sh

It is nice to use to convert all your large overlays you sync to gx86, etc.

The script does not handle case of multiline description:
    DESCRIPTION="You have to
    clean that yourself."

I'll mangle/commit one package at a time. Hope not to interfere with your
workflow much.

If you have any objections/thoughts please do say so.

Thanks!

-- 

  Sergei

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2014-08-11 20:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 12:22 Sergei Trofimovich [this message]
2014-08-11 20:34 ` [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Bertrand Jacquin
2014-08-12 18:32   ` Michał Górny
2014-08-12  1:48 ` William Hubbs
2014-08-12  1:59   ` Manuel Rüger
2014-08-12  2:42     ` William Hubbs
2014-08-12  4:20       ` Tyler Pohl
2014-08-12  5:29         ` [gentoo-dev] " Duncan
2014-08-12 11:33           ` Alex Xu
2014-08-12 12:47       ` [gentoo-dev] " hasufell
2014-08-12 13:26         ` Rich Freeman
2014-08-12 14:26           ` hasufell
2014-08-12 16:24           ` William Hubbs
2014-08-12 18:37           ` Chris Reffett
2014-08-12 21:08             ` hasufell
2014-08-12 13:54         ` Ian Stakenvicius
2014-08-12 14:04           ` [gentoo-dev] repoman --nonag (was Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings ) Ian Stakenvicius
2014-08-12 16:36             ` Rich Freeman
2014-08-12 16:57               ` Ian Stakenvicius
2014-08-12 17:08                 ` hasufell
2014-08-12 17:13                   ` Ian Stakenvicius
2014-08-12 17:25                     ` Rich Freeman
2014-08-12 17:46                       ` William Hubbs
2014-08-12 19:01             ` Michał Górny
2014-08-12 19:11               ` Ian Stakenvicius
2014-08-13  8:47             ` Tom Wijsman
2014-08-12 18:46   ` [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Michał Górny
2014-08-18 14:10     ` Ben de Groot
2014-08-13  8:38   ` Tom Wijsman
2014-08-13 16:36     ` [gentoo-dev] " Duncan
2014-08-12 22:00 ` [gentoo-dev] " Alexander Berntsen

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=20140810152211.2cc5ae94@sf \
    --to=slyfox@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