From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Alexandru Vaduva <Alexandru.Vaduva@enea.com>,
"meta-virtualization@yoctoproject.org"
<meta-virtualization@yoctoproject.org>
Cc: "vu.tran@windriver.com" <vu.tran@windriver.com>
Subject: Re: meta-openstack open-iscsi question
Date: Tue, 29 Jul 2014 08:50:27 -0400 [thread overview]
Message-ID: <53D79893.3090705@windriver.com> (raw)
In-Reply-To: <DDB0C57E45663A458C5CACB7B5688BC21D6D568D@SESTOEX04.enea.se>
On 14-07-29 08:44 AM, Alexandru Vaduva wrote:
> Hello guys,
>
> I am curious on why do you have in meta-cloud-services duplicated recipes:
> open-iscsi-user - iscsi-initiator-utils
We have modifications to this recipe that I'm working to get into the
original over time.
But I can't hold merging dependent recipes while I wait, so I carry
the changes in meta-cloud-services while that process happens.
> open-iscsi-kernel - kernel with open iscsi modules enabled and built.
>
> I can see that the sources available for open-iscsi-kernel are applicable for kernel version < 3,
The kernel part is only there for completeness sake. We build the
kernel parts from the linux-yocto recipes. Over time, we'll also
be dropping this part .. as Vu knows, I already asked him and am
in the process of removing it.
> But I do not understand the uses of both open-iscsi-user and iscsi-initiator-utils because they are building the same information but different version of the sources.
> At least so it seems.
Again. For completeness sake. We brought in a complete copy of the
HIPOS recipes to work with as part of enabling the backend. That
way I can more easily keep it in sync.
Bruce
>
>
> Thanks,
> Alexandru Vaduva
>
>
>
>
>
next prev parent reply other threads:[~2014-07-29 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 12:44 meta-openstack open-iscsi question Alexandru Vaduva
2014-07-29 12:50 ` Bruce Ashfield [this message]
2014-07-29 12:51 ` Alexandru Vaduva
2014-07-29 12:58 ` Bruce Ashfield
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=53D79893.3090705@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=Alexandru.Vaduva@enea.com \
--cc=meta-virtualization@yoctoproject.org \
--cc=vu.tran@windriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.