public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Re: manually creating manifests with RESTRICT="fetch"
Date: Sat, 13 Aug 2011 00:23:21 +0300	[thread overview]
Message-ID: <CAHNvW1Lg6hzRBcaWpYPtmoQbGeeke+bhgcFhuras6W1ZyPUSmA@mail.gmail.com> (raw)
In-Reply-To: <CAF4BF-QbQrTEYuHiZuSiOZXhNuA6rhwe4m5wfib_KwK=d5NyOQ@mail.gmail.com>

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

On Fri, Aug 12, 2011 at 9:55 PM, Christopher Friedt
<chrisfriedt@gmail.com>wrote:

> On Fri, Aug 12, 2011 at 2:48 PM, Christopher Friedt
> <chrisfriedt@gmail.com> wrote:
> > Is there any way to generate the manifest file using 'ebuild' so that
> > it will just read the files from my DISTDIR rather than trying to
> > fetch them?
>
> Got it...
>
> FETCHCOMMAND="echo" ebuild A/B/B.ebuild digest
>
> 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

This is much better way to do it.

Regards,
Kfir

[-- Attachment #2: Type: text/html, Size: 1459 bytes --]

  reply	other threads:[~2011-08-12 21:24 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 [this message]
2011-08-12 23:00     ` Christopher Friedt
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=CAHNvW1Lg6hzRBcaWpYPtmoQbGeeke+bhgcFhuras6W1ZyPUSmA@mail.gmail.com \
    --to=lavi.kfir@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