From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B92F51387C3 for ; Fri, 1 Feb 2013 11:08:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 97E82E067D; Fri, 1 Feb 2013 11:07:56 +0000 (UTC) Received: from spot.xmw.de (spot.xmw.de [176.9.87.236]) by pigeon.gentoo.org (Postfix) with ESMTP id 74B2DE0665 for ; Fri, 1 Feb 2013 11:07:55 +0000 (UTC) Received: from [IPv6:2001:6f8:1cd1:0:21d:72ff:fe88:9ac1] (x.l.xmw.de [IPv6:2001:6f8:1cd1:0:21d:72ff:fe88:9ac1]) by spot.xmw.de (Postfix) with ESMTPSA id B74D614410AFF for ; Fri, 1 Feb 2013 12:07:54 +0100 (CET) Message-ID: <510BA201.20002@gentoo.org> Date: Fri, 01 Feb 2013 12:07:45 +0100 From: Michael Weber User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130114 Thunderbird/17.0.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: readme.gentoo.eclass: use echo -e instead of plain echo (Was: Re: [gentoo-dev] readme.gentoo.eclass: Add a DISABLE_AUTOFORMATTING variable= References: <1359295221.2927.24.camel@belkin4> <1359308848.2927.32.camel@belkin4> <1359658743.26423.13.camel@belkin4> In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 8dfefc5f-987b-4edb-8524-d5469d4b5acb X-Archives-Hash: 3133fb151b973f470e1acd4ff563742a On 02/01/2013 10:55 AM, Ben de Groot wrote: > On 1 February 2013 02:59, Pacho Ramos wrote: >> El dom, 27-01-2013 a las 18:47 +0100, Pacho Ramos escribió: >>> El dom, 27-01-2013 a las 15:00 +0100, Pacho Ramos escribió: >>>> Currently, when people uses DOC_CONTENTS variable to place their desired >>>> messages, they are automatically reformatted by "fmt" to get proper >>>> messages (for example, splitting long lines). >>>> >>>> But, in some cases, may be useful to disable this behavior and respect >>>> strictly how DOC_CONTENTS was formatted, for example in that kind of >>>> messages telling people to run a command and, then, requiring a new line >>>> to be used. This can also be useful to append extra information to >>>> DOC_CONTENTS when, for example, additional info is needed when enabling >>>> a USE flag. >>>> >>>> >>> >>> Well, after reading man echo I see all this is not needed, I simply need >>> to use echo -e to get it understand "\n" to create new lines >>> >>> New patch attached >> >> This will add an option to disabling autoformatting to let people get >> their doc_contents 100% respected if they want > > How about using an "as-is" argument to readme.gentoo_create_doc? > That would be more concise. :-) > PLEASE, add "define DOC_CONTENTS in an non-global scope, use src_prepare/pkg_setup instead" to the eclass documentation of readme.gentoo_print_elog, Thanks ++ for the eclass, the README.gentoo might submerge into the users handling of Gentoo Systems. (I always laughed about README.Debian) [1] show an report about exactly the non-atomar situation of elog and application usage. While [2] complained about elog cluttering, I try to migrate x11-wm/xpra-0.8.0 (upcoming), am I doing it right? DOC_CONTENTS=""" please make your Xorg binary readable for users of xpra chmod a+r /usr/bin/Xorg and think about the security impact A copy at ~/.xpra/Xorg matching the current modules is sufficient. """ ^^ clearly would benefit from non-formatting. repoman full complains about "Ebuild contains leading spaces on line". [1] https://bugs.gentoo.org/show_bug.cgi?id=448588 [2] https://bugs.gentoo.org/show_bug.cgi?id=440464 -- Michael Weber Gentoo Developer web: https://xmw.de/ mailto: Michael Weber