All of lore.kernel.org
 help / color / mirror / Atom feed
From: Måns <mans.zigher@gmail.com>
To: Ross Burton <ross@burtonini.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [Question] How to handle GPLv3 packages?
Date: Fri, 8 Apr 2022 10:18:22 +0200	[thread overview]
Message-ID: <CAEhQi8=Fem0HnTbhK7evENES4qpcC2-pbRicW52YrvwHbegj_Q@mail.gmail.com> (raw)
In-Reply-To: <CAAnfSTvP+aHDxBSSSNVLejxhMPr9NJ4FuYLXDTmaPifBKmGL3w@mail.gmail.com>

Hi Ross,

We don't have a ptest set in DISTRO_FEATURE so if that is the only way
to pull in ptest I would say that is the reason for us at least on why
there are so many bash dependencies.
One recipe that I am looking into right now is util-linux which does
have package util-linux-bash-completion but even the package
util-linux seems to depend on bash and bash-completion when
checking the dependencies by running bitbake -g util-linux and bitbake
-g <image>. It is not clear why the package util-linux depends on bash
and bash-completion. I have other recipes where it is also
not obvious to me why they have a dependency to bash and
bash-completion. One such recipe is a recipe that we have created and
the only content in the package produced is a script and the script
only has #!/bin/sh so not sure where this bash and bash-completion
comes from it is not something we have added so maybe we have some
underlying issue here that results in so many dependencies to
bash and bash-completion. We have not set up this system ourselves,
instead one of the HW suppliers starting with a Q ending with COMM
which I must say I am not that impressed with has supplied the
base that we are building on.

Thanks for your help anyway.


Den ons 6 apr. 2022 kl 11:11 skrev Ross Burton <ross@burtonini.com>:
>
> On Wed, 6 Apr 2022 at 09:59, Mans Zigher <mans.zigher@gmail.com> wrote:
> > A more specific issue is that there are so many packages with bash
> > dependencies which are pulling in bash which is GPLv3 so how have you
> > solved that? Currently we have done some pretty uggly hacks which I am
> > not that happy with but we needed to keep it out of the image.
>
> As you're not naming recipes it is hard to offer concrete advice, but
> I will note that a large percentage of the bash dependencies in
> oe-core are specific to the ptest packages. If you don't need those
> then you can turn off the ptest DISTRO_FEATURE.
>
> Ross


  reply	other threads:[~2022-04-08 17:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  8:59 [Question] How to handle GPLv3 packages? Måns
2022-04-06  9:03 ` [yocto] " Alexander Kanavin
2022-04-08  6:06   ` Måns
2022-04-08  8:15     ` Alexander Kanavin
2022-04-08 16:56       ` Måns
2022-04-08 16:59         ` Alexander Kanavin
2022-04-11  7:12           ` Måns
2022-04-11  7:16             ` Alexander Kanavin
2022-04-11  8:29               ` Måns
2022-04-11 16:19                 ` Khem Raj
2022-04-12  9:45                   ` Måns
2022-04-06  9:10 ` Ross Burton
2022-04-08  8:18   ` Måns [this message]
2022-04-08  8:22     ` Alexander Kanavin
2022-04-08  8:32     ` Mikko.Rapeli
2022-04-08  9:22       ` Alexander Kanavin
2022-04-08 10:17         ` Måns
2022-04-06  9:23 ` Mikko.Rapeli
2022-04-06  9:31   ` Måns

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='CAEhQi8=Fem0HnTbhK7evENES4qpcC2-pbRicW52YrvwHbegj_Q@mail.gmail.com' \
    --to=mans.zigher@gmail.com \
    --cc=ross@burtonini.com \
    --cc=yocto@lists.yoctoproject.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 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.