From: Christopher Friedt <chrisfriedt@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Re: manually creating manifests with RESTRICT="fetch"
Date: Fri, 12 Aug 2011 19:00:07 -0400 [thread overview]
Message-ID: <CAF4BF-TY4u+LAJ2pyYbDTP7ew3ttker88WdHR4Cahg3y0EdsCQ@mail.gmail.com> (raw)
In-Reply-To: <CAHNvW1Lg6hzRBcaWpYPtmoQbGeeke+bhgcFhuras6W1ZyPUSmA@mail.gmail.com>
On Fri, Aug 12, 2011 at 5:23 PM, Kfir Lavi <lavi.kfir@gmail.com> wrote:
> But this is not the solution!
> I have the same tree for my embedded systems, and I do the same as you.
> My header looks like this:
> EAPI="3"
> inherit cmake-utils flag-o-matic
> MY_P="${P}-Source"
> SRC_URI="${MY_P}.tar.bz2"
> RESTRICT="fetch" # This file resides locally and can't be fetched
>
> Please check the EAPI you use, maybe it needs to change.
> Also look close on the SRC_URI, it has just the name of the file.
> I'm also using repoman to generate all my manifests like this:
> cd portage_local_tree; repoman -f manifest
Hmm... I'm using EAPI=4 in this ebuild. The SRC_URI is OK, since it
works with FETCHCOMMAND=echo and properly hashes the files in DISTDIR.
The inherit line is unnecessary AFAIK.
I wouldn't doubt that it was a bug in the portage version I'm using.
It's been 43 days since my last emerge --sync, but I can't update ATM
because I don't want to break any APIs in the (rather large) project
I'm building right now.
Oh well - problem has been solved anyway.
C
next prev parent reply other threads:[~2011-08-12 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 18:48 [gentoo-embedded] manually creating manifests with RESTRICT="fetch" Christopher Friedt
2011-08-12 18:55 ` [gentoo-embedded] " Christopher Friedt
2011-08-12 21:23 ` Kfir Lavi
2011-08-12 23:00 ` Christopher Friedt [this message]
2011-08-13 7:14 ` Kfir Lavi
2011-08-13 12:17 ` Peter Volkov
2011-08-13 12:26 ` Christopher Friedt
2011-08-13 14:23 ` Christopher Friedt
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=CAF4BF-TY4u+LAJ2pyYbDTP7ew3ttker88WdHR4Cahg3y0EdsCQ@mail.gmail.com \
--to=chrisfriedt@gmail.com \
--cc=gentoo-embedded@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