public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Friedt <chrisfriedt@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] manually creating manifests with RESTRICT="fetch"
Date: Fri, 12 Aug 2011 14:48:46 -0400	[thread overview]
Message-ID: <CAF4BF-RhUSsBa3_raofGSBJZPJGSvfQGw=6xetAXrw_wg5MbVg@mail.gmail.com> (raw)

I'm trying to create a couple of ebuilds (for embedded devices) where
the files from SRC_URI must be manually downloaded after accepting the
conditions of a license.

Even after I've downloaded the files, to DISTDIR
(/usr/portage/distfiles), ensuring that they are entered in my SRC_URI
variable, with the RESTRICT=fetch keyword, I'm unable to generate
manifests for the files using "ebuild A/B/B.ebuild digest" because it
tries to fetch the files anyway.

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?

The "--force" option does not help, nor does the
FEATURES="assume-digest" or FEATURES="digest".

"arm*-emerge --version" is

Portage 2.1.9.42 (default/linux/arm/10.0, gcc-4.4.5, unavailable, 3.0.0 x86_64

Cheers,

Chris



             reply	other threads:[~2011-08-12 18:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 18:48 Christopher Friedt [this message]
2011-08-12 18:55 ` [gentoo-embedded] Re: manually creating manifests with RESTRICT="fetch" Christopher Friedt
2011-08-12 21:23   ` Kfir Lavi
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='CAF4BF-RhUSsBa3_raofGSBJZPJGSvfQGw=6xetAXrw_wg5MbVg@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