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] Re: gentoo-x86 commit in app-forensics/memdump: memdump-1.0.1.ebuild ChangeLog
Date: Tue, 06 Jan 2009 12:08:25 +0300	[thread overview]
Message-ID: <1231232905.5292.74.camel@localhost> (raw)
In-Reply-To: <8b4c83ad0901050025k2356e1e4nbf40ea3fe86b7a57@mail.gmail.com>


Daniel, answering you in this mail... Yes, probably sometimes we have to
discuss basic things in this mailing list but since developers do this
basic errors we have to. Technical problems in our portage tree are
perfectly valid for this mailing list.

В Пнд, 05/01/2009 в 13:55 +0530, Nirbheek Chauhan пишет:
> >> SRC_URI="http://www.porcupine.org/forensics/${PN}-1.01.tar.gz"                                                    ~~~~
> 
> Missing MY_PV I presume?

Hardcoded version makes version bumps harder. I'm not sure why ebuild
was versioned differently from tarbal but yes, in this case it's better
to use versionator eclass define PV.

> >> RDEPEND="virtual/libc"
> >  ^^^^^^^^^^^^^^^^^^^^^^
> 
> Useless deps which are already in @system?

Dependency on libc is completely useless since every usable system have
C library.

> >> S=${WORKDIR}/${PN}-1.01
> >                     ~~~~
> 
> Quotes and ${MY_PV} missing?

You don't need quotes in assignments. It hardcoded version again.

> >> src_compile() {
> >>       cd ${S}/memdump-1.01
> >          "    "        ~~~~
> 
> Quotes, and ${PN}-${MY_PV} ?
> Although, should this even be required since ${S} is already set correctly?

src_compile initial working directory is S so this line could (and
should) be just dropped.

> >>               einfo "testing"
> >>               if [ "`./memdump -s 344 | wc -c`" = "344" ];
> >>               then
> >>                       einfo "passed test"
> >>               else
> >>                       die "failed test"
> >>               fi
> 
> Here, why not use
> 
> einfo "testing"
> [ "`./memdump -s 344 | wc -c`" = "344" ] || die "failed test"
> einfo "passed test"

Yup. It's shorter and does same thing.

-- 
Peter.




  reply	other threads:[~2009-01-06  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1LJcf9-00025P-UZ@stork.gentoo.org>
2009-01-05  0:07 ` [gentoo-dev] Re: gentoo-x86 commit in app-forensics/memdump: memdump-1.0.1.ebuild ChangeLog Torsten Veller
2009-01-05  8:25   ` Nirbheek Chauhan
2009-01-06  9:08     ` Peter Volkov [this message]
2009-01-05 11:15   ` list purpose. was: " Daniel Black
2009-01-05 16:29     ` Mark Loeser
2009-01-05 23:50       ` [gentoo-dev] Re: list purpose. was: " Duncan

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=1231232905.5292.74.camel@localhost \
    --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