| 1 |
On Mon, 11 Aug 2014 20:48:20 -0500 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> On Sun, Aug 10, 2014 at 03:22:11PM +0300, Sergei Trofimovich wrote: |
| 5 |
> > Hello World! |
| 6 |
> > |
| 7 |
> > TL;DR: |
| 8 |
> > This evening I plan to mangle ~3000 ebuilds in the main tree |
| 9 |
> > by dropping trailing '.' in all 'DESCRIPTION=' fields (except |
| 10 |
> > "etc." case) |
| 11 |
> > |
| 12 |
> > Long story: |
| 13 |
> > |
| 14 |
> > As you may know newest portage release 2.2.11 |
| 15 |
> > got a minor (but chatty) QA warning: |
| 16 |
> > DESCRIPTION ends with a '.' character |
| 17 |
> |
| 18 |
> Why is this a QA warning in the first place? |
| 19 |
|
| 20 |
It isn't or shouldn't be; in the future, it would be nice if this type |
| 21 |
passes by QA / Council before being acked into the Portage tree code. |
| 22 |
|
| 23 |
Looking at the commit, the ack / commit has completely bypassed QA; we |
| 24 |
also were not involved on the related bug, thus we were unaware of it. |
| 25 |
|
| 26 |
> I don't recall a policy mandating that descriptions can't end with |
| 27 |
> '.'. I asked our QA lead about it and was told that he didn't recall |
| 28 |
> that we have an official policy about it either. Also, the devmanual |
| 29 |
> never mentions any such requirement. |
| 30 |
|
| 31 |
It has been a common belief to drop '.' among some from what I've seen. |
| 32 |
|
| 33 |
-- |
| 34 |
With kind regards, |
| 35 |
|
| 36 |
Tom Wijsman (TomWij) |
| 37 |
Gentoo Developer |
| 38 |
|
| 39 |
E-mail address : TomWij@g.o |
| 40 |
GPG Public Key : 6D34E57D |
| 41 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives