public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "William A. Mills" <wm.a.mills@gmail.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: New user feedback
Date: Fri, 24 Nov 2017 15:47:04 +0100	[thread overview]
Message-ID: <20171124154704.7295a6e2@md1em3qc> (raw)
In-Reply-To: <CACgK+xmeuk=2YEHv1zkrALcehKkJCs4EHfdBUKdG14RcTe-ZFA@mail.gmail.com>

Hi Bill,

thanks for your feedback!

Am Thu, 23 Nov 2017 08:51:40 -0500
schrieb "William A. Mills" <wm.a.mills@gmail.com>:

> Hi,
> 
> I am Bill Mills from TI.  I can't use my @ti.com e-mail address on
> this forum or github project so I will be using this gmail one at
> least for now.
> 
> Getting hands on with ISAR has been on my TODO list since DebConf in
> Montreal.  I finally got around to this last Wednesday (11/15).
> 
> I have been using OE since 2008 and Yocto Project since its
> inception.  I am a log time Ubuntu user so I consider myself a
> decently knowledgeable power user for Debian style distros.
> 
> The above is to give you some context.  It is also to show that I
> have more experience than many of your potential users.
> 
> The good news:
> 
> In a fresh Debian Jessie VM I had no problem following your
> directions and getting builds for QEMU armhf, i386, and amd64.
> 
> A good number of the problem I found and worked around were fixed in
> the push to master on Nov 17:  rerepro & python package dependences,
> misplaced proc mount, clean up of dev and proc mounts on failure,

Good to hear that.
 
> The improvements I think you could make for new users:
> 
> 1) The user documentation should say what host distros are supported.

...

good point
  
> 2) The user documentation should guide the user to setup a new VM (or
> container) to do the work in.
 
True. We at Siemens actually do build in docker and we should share how
we do that. Actually the images are public just the commands might not
be.

Try that on any host-Linux running docker:

$ docker run -e USER_ID=$(id -u) --rm -t -i  --cap-add=SYS_ADMIN
--device $(/sbin/losetup -f) --cap-add=MKNOD -e http_proxy=$http_proxy
-e https_proxy=$https_proxy -e ftp_proxy=$ftp_proxy -e
no_proxy=$no_proxy kasproject/kas-isar bash

builder@..$ git clone https://github.com/ilbers/isar.git
  cd isar
  . ./isar-init-build-env ../build
builder@..:~/build$ bitbake
multiconfig:qemuamd64-stretch:isar-image-base

> 3) Provide extra host configuration guidance
> 
> I know how to enable jessie-backports but I am not sure everyone will.

Well the prefered way would be stretch+ anyways.

> Some methods of getting a clean VM leaves the locales unconfigured
> which causes a problem with bitbake.  I use:
> sudo dpkg-reconfigure locales
> 
> and then pick en_US.UTF-8 UTF8 from the text menu.
> I think there are better ways also.

Patches for this are currently under discussion.

> 4) Provide a build dir delete script or task

If you use "docker run --rm" that is not a problem, but you are right.

...
 
> -------
> 
> Should I create issues for these 4 items?
> 
> This is my feedback so far.
> I did read over the recipes, classes and main scripts and have a
> decent understanding of the basics.
> 
> Thanks for your attention.
> Bill
> 


      parent reply	other threads:[~2017-11-24 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 13:51 William A. Mills
2017-11-24 13:59 ` Baurzhan Ismagulov
2017-11-24 14:47 ` Henning Schild [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=20171124154704.7295a6e2@md1em3qc \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=wm.a.mills@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox