public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: fox.eclass update
Date: Thu, 16 Sep 2010 22:32:29 +0400	[thread overview]
Message-ID: <1284661949.14378.289.camel@tablet> (raw)
In-Reply-To: <4C922892.6040500@gentoo.org>

В Чтв, 16/09/2010 в 16:24 +0200, Matti Bickel пишет:
> +FOXVER=`get_version_component_range 1-2 ${FOX_PV}`

It's better to prefer $() style over ``:
http://mywiki.wooledge.org/BashFAQ/082

>  if [ "${PN}" != fox ] ; then
>         FOX_COMPONENT="${FOX_COMPONENT:-${PN}}"
>  fi
>  
> -if [ "${FOXVER}" != "1.0" ] && [ -z "${FOX_COMPONENT}" ] ; then
> +if [ -z "${FOX_COMPONENT}" ] ; then
>         DOXYGEN_DEP="doc? ( app-doc/doxygen )"
>  fi

It's better to use [[ ]] and avoid quotes since ebuilds are bash
scripts.

> -       elibtoolize
> +       eautoreconf

Hm, is this change necessary?

> +       if ( ! use doc ) && [ -d "${D}/usr/share/doc/${PF}/html" ] ;
> then

Subshell looks redundant here.

> +               epause

It's better to avoid epause as it makes build slower at the same time
it's most probable that nobody is looking on the screen at the moment[1]
and portage will print all elog messages at the end of the build in any
case.
 
[1] while emerge output is one of those things one can observe for ages
(like water, fire and others working) still it's possible no one
thoughtfully staring at the screen...

-- 
Peter.




  parent reply	other threads:[~2010-09-16 19:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 13:31 [gentoo-dev] RFC: fox.eclass update Matti Bickel
2010-09-16 13:39 ` Tomáš Chvátal
2010-09-16 14:24 ` Matti Bickel
2010-09-16 14:41   ` Jeremy Olexa
2010-09-16 15:44     ` Jeroen Roovers
2010-09-16 17:38       ` Peter Volkov
2010-09-16 16:48     ` Matti Bickel
2010-09-16 18:32   ` Peter Volkov [this message]
2010-09-16 18:51     ` Matti Bickel
2010-09-16 19:29       ` Mike Frysinger
2010-09-16 19:41         ` Peter Volkov
2010-09-16 22:34           ` Mike Frysinger
2010-09-17  3:51             ` [gentoo-dev] " Ryan Hill
2010-09-17  4:56               ` Mike Frysinger
2010-09-17  5:06             ` [gentoo-dev] " Peter Volkov
2010-09-17  5:24               ` Mike Frysinger
2010-09-16 20:24         ` Matti Bickel
2010-09-16 22:33           ` Mike Frysinger
2010-09-17  8:15     ` Michael Haubenwallner
  -- strict thread matches above, loose matches on Subject: below --
2008-10-12 12:41 Matti Bickel
2008-10-13 10:56 ` Petteri Räty
2008-10-13 17:20   ` Donnie Berkholz
2008-10-13 18:28     ` Matti Bickel
2008-10-14 13:20       ` Bo Ørsted Andresen
2009-02-08 22:06         ` Matti Bickel
2009-02-09 15:01           ` Peter Volkov
2009-02-09 18:22             ` Matti Bickel
2009-02-10  5:10               ` Nirbheek Chauhan

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=1284661949.14378.289.camel@tablet \
    --to=pva@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