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
Cc: phajdan.jr@gentoo.org
Subject: Re: [gentoo-dev] haskell-cabal.eclass suggestions
Date: Sat, 31 Mar 2012 12:20:06 +0300	[thread overview]
Message-ID: <20120331122006.0809cf3e@sf.home> (raw)
In-Reply-To: <4F75A00E.3060006@gentoo.org>

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

On Fri, 30 Mar 2012 13:59:10 +0200
""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> wrote:

> >     echo 'import Distribution.Simple; main = defaultMainWithHooks defaultUserHooks' \
> >         > $setupdir/Setup.hs
> > }
> 
> I think there should be || die after echo, to catch out-of-disk-space
> problems.

Ok :]

> >     # GHC 6.4 has a bug in get/setPermission and Cabal 1.1.1 has
> >     # no workaround.
> >     # set the +x permission on executables
> >     if [[ -d "${ED}/usr/bin" ]] ; then
> >         chmod +x "${ED}/usr/bin/"*
> >     fi
> >     # TODO: do we still need this?
> > }
> 
> I think there should be || die after chmod.

I'll remove the whole block.

> >     if [[ -z "${CABAL_HAS_BINARIES}" ]] && [[ -z "${CABAL_HAS_LIBRARIES}" ]]; then
> >         eerror "QA: Neither bin nor lib are in CABAL_FEATURES."
> 
> Shouldn't this be eqawarn?
> 
> >     fi
> >     if [[ -n "${CABAL_UNKNOWN}" ]]; then
> >         ewarn "Unknown entry in CABAL_FEATURES: ${CABAL_UNKNOWN}"
> 
> Shouldn't this be eqawarn?

'eqawarn' sounds fine here. I'll push the changes to overlay first and then to the gx86.

Thanks for sharing!

-- 

  Sergei

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

      reply	other threads:[~2012-03-31  9:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 11:59 [gentoo-dev] haskell-cabal.eclass suggestions "Paweł Hajdan, Jr."
2012-03-31  9:20 ` Sergei Trofimovich [this message]

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=20120331122006.0809cf3e@sf.home \
    --to=slyfox@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=phajdan.jr@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