From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] resolving portage keywords issue from within catalyst?
Date: Thu, 19 Dec 2013 01:48:50 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1312190142320.27394@woodpecker.gentoo.org> (raw)
In-Reply-To: <CACU8XWk7b_=UsEKr2fEyvUpK9UAO5SYUcmWHz5K+DKtHmwK8dA@mail.gmail.com>
On Wed, 18 Dec 2013, lin pro wrote:
> Hi,
Hi.
> Here is the spec file that is causing trouble http://bpaste.net/show/159985/
> Catalyst stop with this message:
>
> The following keyword changes are necessary to proceed:
> (see "package.accept_keywords" in the portage(5) man page for more details)
> # required by dev-ml/ocaml-mad (argument)
> =dev-ml/ocaml-mad-0.4.4 ~amd64
>
>
> ...and many more.
>
> Now the /etc/portage/package.keywords has this inside
> grep ocaml-mad /etc/portage/package.*
> /etc/portage/package.keywords:dev-ml/ocaml-mad ~amd64
>
> Even if I put put the keyword in package.accep_keywords the behaviour
> of catalyst is the same.
> It seems that catalyst does not read those files for me.
>
> Thank you for hints
Catalyst doesn't use any of the /etc/portage files on your host. You need
to use the portage_confdir var in the spec files to tell catalyst to use
it when building the stage.
You can check an example of its use in releng's official repository[1].
You can see how we use it on the installcd specs[2][3] and an example of
the portage config dir for the installcd[4] and the admincd[5].
[1] - http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git
[2] -
http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=blob;f=releases/weekly/specs/amd64/installcd-stage1.spec;h=0bb6777efd2c6151edae44250d1ba708ec929784;hb=refs/heads/master
[3]
-http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=blob;f=releases/weekly/specs/amd64/installcd-stage2-minimal.spec;h=9f2a231c7c9f2eb36ff934a01a900c196c3998f6;hb=refs/heads/master
[4] -
http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=tree;f=releases/weekly/portage/installcd;h=cf9e9fd3c801e505b23f2c57c9689a93c6094313;hb=refs/heads/master
[5] -
http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=tree;f=releases/weekly/portage/admincd;h=3c2b52a416aa991af1b246bc12dec902b08b4139;hb=refs/heads/master
> Ben
Regards,
Jorge
prev parent reply other threads:[~2013-12-19 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 0:07 [gentoo-catalyst] resolving portage keywords issue from within catalyst? lin pro
2013-12-19 1:43 ` Rick "Zero_Chaos" Farina
2013-12-19 1:48 ` Jorge Manuel B. S. Vicetto [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=alpine.LNX.2.00.1312190142320.27394@woodpecker.gentoo.org \
--to=jmbsvicetto@gentoo.org \
--cc=gentoo-catalyst@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