From: Ed W <lists@wildgooses.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] ebuild deps and cross-compiling
Date: Fri, 23 Apr 2010 15:50:42 +0100 [thread overview]
Message-ID: <4BD1B3C2.9090604@wildgooses.com> (raw)
In-Reply-To: <k2uaa09d86e1004230420h88b4d66i22fd6c12e416d7a0@mail.gmail.com>
On 23/04/2010 12:20, Sergey Mironov wrote:
> My system doesn't have udev. It has mdev from busybox. Openct docs
> says that mdev is ok, so should i register an ebuild-bug and suggest
> something like 'udev useflag'? There are util-linux dependencies,
> which are also incompatible with busybox. I am in doubt.
>
>
The "gentoo" way as near as I can see is via virtual packages, eg if
there are three cron options then you install virtual/cron and various
packages then provide that dependency.
With udev it's a little harder to fit it into that mould (actually same
with all busybox utils) because basically bb can provide different
things depending on config...
I think it's a hard problem to solve and a small number of affected
users. Probably as a workaround you should simply set package.provided
to claim you have installed udev and then all the dependencies are
effectively assumed to be solved. Of course this will break down on
some package that really does need proper udev, but it's probably
acceptable?
A use flag is probably inappropriate because that's usually used to
indicate whether you want that functionality compiled or removed from a
given package
I guess there must be some -arm overlay that you can base from and
contribute to? Anyone?
Good luck
Ed W
next prev parent reply other threads:[~2010-04-23 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:20 [gentoo-embedded] ebuild deps and cross-compiling Sergey Mironov
2010-04-23 14:50 ` Ed W [this message]
2010-04-24 11:26 ` Gentoo
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=4BD1B3C2.9090604@wildgooses.com \
--to=lists@wildgooses.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