[OE-core] Build systems MC at LPC 2024, Vienna - CFP open!

[Josef Holzmayr]

In the Linux ecosystem, there are many ways to build all the software used
to put together a running system. Whether it’s building all the binary
packages for a binary Linux distribution, using a source-based
distribution, or building an embedded system from scratch, there are a lot
of shared challenges which each system solves in its own way.

In the inagural Build Systems people talked about [1]:
 * Providing provenance of build artifacts
 * Checking for UAPI changes between builds
 * Managing Linux kernels for products
 * Tracking patches used in a build
 * Building for hardware that requires building multiple sets of firmware

This microconference is a way to get people who work on disparate build
systems to discuss common problems and possible shared solutions across the
entire problem space. The kinds of topics we want to discuss are the
following:

 * Bootstrapping the build system
 * Cross building software
 * Make, autoconf, and other similar software build tools
 * Package build systems, bitbake, emerge/portage, pacman, etc
 * Packaging formats
 * Managing software with language-specific package managers
 * Patch sharing
 * Building within a container
 * Build systems for building containers
 * License gathering and verification
 * Security updates
 * SBOMS
 * Software chain-of-trust
 * Repeatable builds
 * Extremely long product life cycle support
 * Documentation and education
 * Finding the next generation of maintainers
 * Build-system visibility within the wider Plumbers attendees.

This is not a definitive list, and you are free to post abstracts for other
related topics.

Build Systems microconference would like to gather representatives
(developers and maintainers) from all the various build systems and related
technologies. This is not a definitive list of possible attendees.

 * Android
 * Arch Linux
 * Buildroot
 * ChromeOS
 * Debian
 * Fedora/Redhat
 * Gentoo
 * OpenEmbedded
 * OpenWRT/LEDE
 * Yocto Project
 * Other traditional Binary Packaged distributions

The CFP closes on July 5 and plan to have the schedule complete by July 19.
Please help us (and the plumbers organziers) by submitting topics early.

For more information, feel free to contact the MC Leads:
Philip Balister 
Josef Holzmayr 

Please follow the suggestions from this BLOG post when submitting a CFP for
this track. [2]
Submissions are made via LPC submission system, selecting Track “Build
Systems MC” [3]

[1] https://lpc.events/event/17/sessions/159/#20231114
[2]
https://lpc.events/blog/current/index.php/2023/06/26/the-ideal-microconference-topic-session/
[3] https://lpc.events/event/18/abstracts/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199841): 
https://lists.openembedded.org/g/openembedded-core/message/199841
Mute This Topic: https://lists.openembedded.org/mt/106279865/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [yocto] [Openembedded-architecture] New mailing list for layer patches

[Josef Holzmayr]

Thanks for that initiative Michael and Paul, this is very helpful for the
greater community!

Greets,
Josef

On Wed, Apr 3, 2024 at 4:59 PM Michael Opdenacker via lists.yoctoproject.org
 wrote:

> Hi Paul,
>
> On 4/2/24 at 10:38, Paul Barker wrote:
> > On 28/03/2024 14:36, Ross Burton wrote:
> >> Hi,
> >>
> >> At the moment if a layer doesn’t have enough volume to justify a
> dedicated mailing list for patches (see, for example,
> meta-...@lists.yoctoproject.org )
> then the convention is that the patches can be sent to
> yo...@lists.yoctoproject.org .
> >>
> >> However, that’s also the list that we encourage users of Yocto to use
> for help, so the list has a mix of patches for various layers and people
> asking for help, which isn’t ideal: users who want help don’t want to be
> flooded with patches for layers they’re not using, layer maintainers may
> not want to see the requests for help, and people who want the status
> reports have to receive patches and support.
> >>
> >> The Yocto TSC has been discussing this, and as a solution to this we’ve
> just created a new mailing list: yocto-patc...@lists.yoctoproject.org
> .  This list is specifically
> for Yocto-related projects which don’t have their own mailing list or other
> patch submission process.   We ask that all layers currently using yocto@
> for patches move to yocto-patches@, so that yocto@ can be used purely for
> discussion and other non-patch related subjects.
> > I think this is a great change, along with the new yocto-status@ list
> it will make things easier to follow :)
> >
> > Do you know if yocto-patches@ will be available via lore.kernel.org?
>
> I've just asked them to index the new lists as well as these important
> ones which are missing too:
> https://lists.yoctoproject.org/g/yocto-announce
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
> https://lists.yoctoproject.org/g/automated-testing
> https://lists.yoctoproject.org/g/yocto-security
>
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#197922): 
https://lists.openembedded.org/g/openembedded-core/message/197922
Mute This Topic: https://lists.openembedded.org/mt/105310355/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Yocto status mailing list

[Josef Holzmayr]

Hi all,

Following some discussions and suggestions to improve, the
yocto-sta...@lists.yoctoproject.org mailing list has been created. It will
serve as a low-traffic, high-density list aimed at those who want a big
picture of things going on without getting overwhelmed by patches and their
discussions.

Currently, this mailing list will receive the weekly status report, as
already known from the openembedded-core and yocto mailing lists. If you
are following those and are happy with it, you don't need to change
anything. If you would like to receive only the condensed status, please
join yocto-status. Upon relevant events or decisions additional mails
beyond the weekly report might be sent to this list, but we will keep the
volume very low.

Greets,
Josef
Yocto Project Community Manager

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#197608): 
https://lists.openembedded.org/g/openembedded-core/message/197608
Mute This Topic: https://lists.openembedded.org/mt/105204625/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OE Workshop in Brussels on February 5th - Monday after FOSDEM

[Josef Holzmayr]

Hi you!

Yes, exactly you!

Didn't you want to grab a seat at the OE Workshop in Brussels, the Monday
right after FOSDEM? It's time to hurry up now, there are just a couple of
seats remaining by now. So head over to
https://pretix.eu/OpenEmbedded/OEW24/ and make sure you get one now, or you
might miss out.

And that would be sad, right?

Greets,
Josef

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194298): 
https://lists.openembedded.org/g/openembedded-core/message/194298
Mute This Topic: https://lists.openembedded.org/mt/103936447/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] CFP for OE Workshop extended

[Josef Holzmayr]

We have extended the deadline for the OE Workshop in Brussels, Monday
February 5th until the upcoming Friday, December 22th.

Give the gift of OE and share your knowledge at
https://pretalx.com/oe-ws-2024/cfp

Josef,
Your friendly OE Santa Helper

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192634): 
https://lists.openembedded.org/g/openembedded-core/message/192634
Mute This Topic: https://lists.openembedded.org/mt/103240805/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OpenEmbedded Workshop CFP - February 5th, 2024

[Josef Holzmayr]

We are hosting a workshop on Monday, February 5th 2024 in Brussels. Yes
exactly, the day right after FOSDEM. So make sure to extend your stay and
share your findings or the things you bring. How? By submitting to the OE
Workshop 2024 CFP. Open now and waiting for you.

https://pretalx.com/oe-ws-2024/cfp

Josef,
on behalf of the OpenEmbedded board

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#189726): 
https://lists.openembedded.org/g/openembedded-core/message/189726
Mute This Topic: https://lists.openembedded.org/mt/102199645/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Yocto Project Summit 2023.11 registrations are open now!

[Josef Holzmayr]

Registration are open now! Join us for the Yocto Project Summit 2023.11 to
not only hear about the latest and greatest, but also challenges and
solutions from the whole community.

https://summit.yoctoproject.org/yocto-project-summit-2023-11/

Josef,
on behalf of the organization committee

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188752): 
https://lists.openembedded.org/g/openembedded-core/message/188752
Mute This Topic: https://lists.openembedded.org/mt/101794917/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Yocto Project Summit CFP closes Monday, October 2nd

[Josef Holzmayr]

The countdown is ticking! At the moment the CFP for the Yocto Project
Summit 2023.11 is still open, but will close on Monday, October 2nd, 2023.
So made sure to submit this weekend!

https://summit.yoctoproject.org/yocto-project-summit-2023-11/cfp

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188408): 
https://lists.openembedded.org/g/openembedded-core/message/188408
Mute This Topic: https://lists.openembedded.org/mt/101659364/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OEDvM / TSC news

[Josef Holzmayr]

Hello my fellow OpenEmbedded aficionados, users, and developers!

You might have noticed that the OEDvM is coming up on December 1st, 2023
(see https://www.openembedded.org/wiki/OEDvM_2023.12)
You also might have noticed that the TSC (Technical Steering Committee)
elections are in full motion already.

If both assumptions apply to you - congratulations!

If not, consider joining the OpenEmbedded organization.
As outlined at https://www.openembedded.org/wiki/Organization#Membership,
it gives you a very direct way to influence the direction of the project.
Not only through code, but also as a person, and an opinion. You are
invited to join, regardless of your affiliation, or your contributions. We
would like to have YOU, as the kind of person that you are.

Feel interested? Reach out to either the board or me, and we are happy to
talk!

Greetz,
Josef - on behalf of the OE board

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187924): 
https://lists.openembedded.org/g/openembedded-core/message/187924
Mute This Topic: https://lists.openembedded.org/mt/101479311/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OEDvM 2023.12

[Josef Holzmayr]

Howdy!

We are happy to announce this years OEDvM taking place on Friday December
1st, 2023.

Bring your topics and challenges for discussion, or just join for the
networking.

As usual, the main organization will happen through the OpenEmbedded Wiki,
with the event page being located at
https://www.openembedded.org/wiki/OEDvM_2023.12


The meeting is open to everybody, and explicitly inviting non-members to
join the conversation, and possibly the organization.

If you have any questions, feel free to reach out!

Greetz,
Josef, on behalf of the OpenEmbedded board

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187664): 
https://lists.openembedded.org/g/openembedded-core/message/187664
Mute This Topic: https://lists.openembedded.org/mt/101376508/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] The YPS 2023.11 CFP is waiting for you!

[Josef Holzmayr]

Summer vacation is over, so what is the next thing to focus on? Sharing
your The Yocto Project, A Linux Foundation Project Kung-Fu, war stories,
use cases...

And the best place to do so is the Yocto Project Summit 2023.11 - the CFP
is already open. We are eager to read your submissions!

https://summit.yoctoproject.org/yocto-project-summit-2023-11/cfp

Deadline is by Monday, October 2nd 2023

Josef
on behalf of the YPS organization committee

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187607): 
https://lists.openembedded.org/g/openembedded-core/message/187607
Mute This Topic: https://lists.openembedded.org/mt/101339467/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] CFP for YPS 2023.11 now open!

[Josef Holzmayr]

Its sunny, it is summer, you're just back from vacation? Nothing better to
get into the flow again than writing a proposal for the 2023.11 edition of
the Yocto Project Summit!

We love to hear about all your Yocto things. What you made, what you broke,
what you learned, what you created.

The CFP is open now at https://pretalx.com/yocto-project-summit-2023-11/cfp

Josef on behalf of the YPS organization team

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186573): 
https://lists.openembedded.org/g/openembedded-core/message/186573
Mute This Topic: https://lists.openembedded.org/mt/100913071/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Yocto Project Community Manager updates

[Josef Holzmayr]

Thank you Nico for the five years in which we had the pleasure of working
together for the growth and future of the Yocto Project and OpenEmbedded.
Your contributions and insight will be missed - but hopefully not you as a
person. We will meet again, over a drink, and talk of the olde times...

And on the same note, thank you Andy, Richard, and all of the leadership
working group for the trust placed in me. Let us make this a change that
keeps the good and adds more of it.

Greetz,
Josef

On Thu, May 4, 2023 at 5:07 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Thu, 2023-05-04 at 16:40 +0200, Nicolas Dechesne wrote:
> > After five years, I have decided to resign from my position as the
> > Yocto Project Community Manager. I joined the OpenEmbedded community
> > around 2008. I have fond memories of my early days, and still
> > remember some of my first interactions on IRC and mailing lists! This
> > is a very welcoming community, always helping new people with
> > patience and kindness. Serving the project during the last five years
> > is something I am very proud of, and I will be forever grateful to
> > all of you for accepting me!
>
> I know we've talked but I did want to publicly say thanks for
> everything you've done in the role!
>
> We've had some good times and overcome some challenges in the last few
> years, the project has definitely benefited from your involvement and
> you'll be sorely missed.
>
> Welcome to the role Josef, no pressure! :)
>
> Cheers,
>
> Richard
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#180880): 
https://lists.openembedded.org/g/openembedded-core/message/180880
Mute This Topic: https://lists.openembedded.org/mt/98685136/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OE Workshop in Brussels, February 6th - gentle reminder

[Josef Holzmayr]

Hello all you Open, Embedded, and even OpenEmbedded people out there!

This is your gentle reminder that we are hosting an OE Workshop in Brussels
on Monday, February 6th - the day after FOSDEM at Avenue Louise 523, 1050
Brussels, Belgium.

Find a preliminary schedule at
https://pretalx.com/openembedded-workshop-2023/featured/ and if you are
around by then, don't forget to register:
https://pretix.eu/OpenEmbedded/workshop-2023/

Greetz,
Josef on behalf of the OE board

PS: lunch will be provided ️

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176134): 
https://lists.openembedded.org/g/openembedded-core/message/176134
Mute This Topic: https://lists.openembedded.org/mt/96375250/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OEDvM and OpenEmbedded Workshop

[Josef Holzmayr]

Hello fellow OpenEmbeddeders!

Less than 24 hours until we kick off the OpenEmbedded Developers virtual
Meeting 2022.11! For more details, please see
https://www.openembedded.org/wiki/OEDvM_2022.11

You can join us directly via https://zoom.us/j/99151508871

Also we have great news: adjacent to FOSDEM, a workshop will take place in
Brussels on February 6th. Be sure to check it out at
https://pretalx.com/openembedded-workshop-2023/ and submit your ideas via
https://pretalx.com/openembedded-workshop-2023/cfp

See you real soon!
Josef on behalf of the OE board

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174060): 
https://lists.openembedded.org/g/openembedded-core/message/174060
Mute This Topic: https://lists.openembedded.org/mt/95382347/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OEDvM 2022.11

[Josef Holzmayr]

Users, contributors, members! [1]

It is about time again to gather - in virtual form - for some hours of
knowledge exchange, discussion, and designing the future of OpenEmbedded.

The OpenEmbedded Developers virtual Meeting 2022.11 will take place on
December 2nd, 2022 [2], and you are invited to not only join, but also
bring your topics. Please find the current outline and subjects at
https://www.openembedded.org/wiki/OEDvM_2022.11 where you can also add your
interests, and step up as moderator/facilitator for existing ones.

No registration is required.

The meeting will be held on Zoom  which is
generously provided by AGL.

See you all there!

Josef, on behalf of the OE board

[1] first one to correctly name the reference gets a small present at the
next in-person event.
[2] we all love a good off-by-one error

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#173344): 
https://lists.openembedded.org/g/openembedded-core/message/173344
Mute This Topic: https://lists.openembedded.org/mt/95042406/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] OEDvM 2022.05

[Josef Holzmayr]

There will be an OpenEmbedded Developer Virtual Meeting (OEDVM) held
on Friday, 20 May 2022.  This will be the day after the Yocto
Project® Summit 2022.05 concludes.  The scheduled time will match the
YP Summit's start at 12 UTC/7AM Eastern, and run until 20 UTC/3PM (or
earlier if we run out of topics, but then will most likely turn into a
happy hour).

The event has been added to the OE Calendar
https://www.openembedded.org/wiki/Calendar

We have added some topics that should be interesting to the larger audience at:
https://www.openembedded.org/wiki/OEDVM_2022_05

We are looking for "moderators" for the currently listed topics.  This
entails helping to get the discussion started by presenting 1-5 slides
on the topic and problems currently being experienced.

If you do not see something listed you would like to discuss, please
add it and put yourself as the "moderator" (and a rough time estimate
for discussion).

As always, if you are not an OpenEmbedded Member (but are interested
in joining), please attend OEDVM and you can be voted in.

If there are any questions, please feel free to email me and/or the
entire OE board (bo...@openembedded.org).

Josef, on behalf of the OpenEmbedded Board

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#165311): 
https://lists.openembedded.org/g/openembedded-core/message/165311
Mute This Topic: https://lists.openembedded.org/mt/90919815/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] report-error: Mask AWS credentials to avoid leaking them

[Josef Holzmayr]

Howdy!

Am 13.07.2021 um 11:22 schrieb Damian Wrobel:

From: Adam Romanek 

Removes potentially presonal information from error reports.

Signed-off-by: Adam Romanek 
Signed-off-by: Damian Wrobel 
---
  meta/classes/report-error.bbclass | 15 ++-
  1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/meta/classes/report-error.bbclass 
b/meta/classes/report-error.bbclass
index de48e4ff0f..c17e7e2851 100644
--- a/meta/classes/report-error.bbclass
+++ b/meta/classes/report-error.bbclass
@@ -38,6 +38,15 @@ def get_conf_data(e, filename):
  jsonstring=jsonstring + line
  return jsonstring
  
+def errorreport_maskvars(e, logdata):

+origenv = e.data.getVar("BB_ORIGENV", False)
+vars_to_mask = ("TOPDIR", "TMPDIR", "AWS_ACCESS_KEY_ID", 
"AWS_SECRET_ACCESS_KEY")
+for var_name in vars_to_mask:
+var_value = e.data.getVar(var_name, True) or (origenv and 
origenv.getVar(var_name, True))
+if var_value:
+logdata = logdata.replace(var_value, var_name)
+return logdata
+
  python errorreport_handler () {
  import json
  import codecs
@@ -82,11 +91,7 @@ python errorreport_handler () {
  try:
  with codecs.open(log, encoding='utf-8') as logFile:
  logdata = logFile.read()
-# Replace host-specific paths so the logs are cleaner
-for d in ("TOPDIR", "TMPDIR"):
-s = e.data.getVar(d)
-if s:
-logdata = logdata.replace(s, d)
+logdata = errorreport_maskvars(e, logdata)
  except:
  logdata = "Unable to read log file"
  else:




This sounds a bit like suggesting that we add a hardcoded magic list of 
masks for possbible places for credentials, and I don't think this is a 
good approach. If at all, then there should be a more generic way that 
doesn't treat S3 as super special.


Greetz






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#153804): 
https://lists.openembedded.org/g/openembedded-core/message/153804
Mute This Topic: https://lists.openembedded.org/mt/84174597/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [Openembedded-architecture] Future of sato and X in oe-core

[Josef Holzmayr]

Howdy!

On Tue, Feb 11, 2020 at 02:57:48PM +0100, Alexander Kanavin wrote:
> The question is: what are the use cases for an 'example/reference UI'? Why
> have one at all at this point? Remember, the core project is severely
> under-staffed and we need to commit our limited resources wisely.

My $.02 are, that while being a good test vehicle to build for us, it is
actually giving a wrong impression to newcomers. Like "here is a DE to
start off, and you can use this build like your desktop box" which is not
at all true.

So my votes are on, as long as we have something that *can* do
*something* on screen with as little effort as possible, we should go
for it. Maintaining a custom thing should be avoided.

Greetz

> 
> On Tue, 11 Feb 2020 at 14:53, Adrian Bunk  wrote:
> 
> > On Tue, Feb 11, 2020 at 01:49:27PM +0100, Alexander Kanavin wrote:
> > >...
> > > - matchbox is reliant on gtk3 (to be obsoleted by gtk4 this year), and
> > does
> > > not have a Wayland compositor. Yocto project does not have the resources
> > to
> > > do the gtk4 port, or add a compositor.
> > >
> > > - no 'lightweight Wayland compositor with a desktop/launcher experience"
> > > has emerged in the open source space; I think the only realistic choice
> > at
> > > the moment is the reference compositor Weston which provides a blank
> > > desktop with ability to open terminal windows.
> > >
> > > So the way I think things should be going (seeking opinions/inputs of
> > > course):
> > >...
> > > - oe-core continues to support and runtime-test X for as long as
> > possible;
> > > for this a new image (say, 'core-image-sato-xorg') is created which will
> > > provide matchbox under X. However, once upstream bitrot sets in, and pain
> > > threshold is exceeded, this will be removed and/or relegated to a legacy
> > > layer.
> > >
> > > Thoughts?
> >
> > matchbox made sense at a time when you could go into a shop and buy an
> > internet tablet with Linux running on 256 MB flash with 256 MB RAM.
> >
> > Part of the problem is that the only remaining usage of this branch
> > of matchbox development seems to be as example UI for Yocto.
> >
> > For matchbox/sato I am wondering whether replacing it with parts of
> > meta-xfce from meta-openembedded would be a good way forward.
> >
> > Upstream Xfce still seems to be 2-3 years away from gtk4 and Wayland
> > support, but at the point where supporting X might become a problem
> > this should be available.
> >
> > Xfce was my first thought as replacement since it appears to be
> > well-maintained in meta-openembedded, no strong opinion whether
> > it is actually the best option.
> >
> > > Regards,
> > > Alex
> >
> > cu
> > Adrian
> >

> ___
> Openembedded-architecture mailing list
> openembedded-architect...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture


-- 
———
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548 

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] OE-Core python minimum version requirement

[Josef Holzmayr]

On Wed, Dec 04, 2019 at 05:45:03PM +, Richard Purdie wrote:
> I just enabled hashequiv's server in local mode by default in poky.
> 
> This causes an unintended side effect of requiring python 3.5 as the
> minimum version.
> 
> We had thought that the servers would be 'rare' and a 3.5 version
> requirement for that was fine. It turns out a local server is also
> extremely useful.
> 
> The code needed the python 3.5 async support and trying to write it any
> other way is a nightmare, we need that performance for the server.
> 
> At this point I think we just give in and require python 3.5 as a
> minimum. Any objections?

A quick check on packages.ubuntu.com says 16.04 is on python 3.5.1,
18.04 is on 3.6.something.

Hence, looks good to me.

Greetz

> 
> Cheers,
> 
> Richard
> 
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
———
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548 

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v2] devtool: add clean command

[Josef Holzmayr]

Add an idiomatic way to devtool to clean a recipe. When using devtool
in the context of an eSDK there is no direct access to bitbake.
This command exposes the bitbake clean facility through devtool,
keeping the idiomatic interface and configurability.

Signed-off-by: Josef Holzmayr <holzm...@rsi-elektrotechnik.de>
---
 scripts/lib/devtool/clean.py | 48 
 1 file changed, 48 insertions(+)
 create mode 100644 scripts/lib/devtool/clean.py

diff --git a/scripts/lib/devtool/clean.py b/scripts/lib/devtool/clean.py
new file mode 100644
index 00..473c30f366
--- /dev/null
+++ b/scripts/lib/devtool/clean.py
@@ -0,0 +1,48 @@
+# Development tool - clean command plugin
+#
+# Copyright (C) 2014-2015 Intel Corporation
+#   2017 R-S-I Elektrotechnik GmbH & Co. KG
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+"""Devtool clean plugin"""
+
+import bb
+from devtool import exec_build_env_command, check_workspace_recipe
+
+def _get_clean_tasks(config):
+tasks = config.get('Clean', 'clean_task', 'clean').split(',')
+return ['do_%s' % task.strip() for task in tasks]
+
+def clean(args, config, basepath, workspace):
+"""Entry point for the devtool 'clean' subcommand"""
+
+build_tasks = _get_clean_tasks(config)
+try:
+bbargs = []
+for task in build_tasks:
+bbargs.append('%s:%s' % (args.recipename, task))
+exec_build_env_command(config.init_path, basepath, 'bitbake %s' % ' 
'.join(bbargs), watch=True)
+except bb.process.ExecutionError as e:
+# We've already seen the output since watch=True, so just ensure we 
return something to the user
+return e.exitcode
+
+return 0
+
+def register_commands(subparsers, context):
+"""Register devtool subcommands from this plugin"""
+parser_build = subparsers.add_parser('clean', help='Clean a recipe',
+ description='Cleans the specified 
recipe using bitbake',
+ group='working', order=50)
+parser_build.add_argument('recipename', help='Recipe to clean')
+parser_build.set_defaults(func=clean)
-- 
2.14.3


-- 
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 0/2] version bump bc to 1.07.1

[Josef Holzmayr]

Hi Jose,

On 25.10.2017 17:16, Jose Lamego wrote:
A previous upgrade attempt [1] showed that bc version 1.07.1 not only 
needs ed in the host (a regression from 1.06) but also shows a Parallel 
Make Race that requires unsetting PARALLEL_MAKE variable. I contacted 
the upstream maintainer and he is aware of this situation and has 
developed and tested a version 1.07.2, (however is not available for 
download yet). The upgrade was delayed for this reason (more details in 
the patch comments thread).


Interesting, thanks for pointing that out!


That said, Is there any urgent need for the upgrade to 1.07.1?


Absolutely not. The story behind this upgrade is that at OEDEM, we 
discussed version bumps as a way for new contributors to get up to 
speed. So when the upgradeable recipes report came in shortly 
afterwards, I just picked something that looked innocent enough and gave 
it a try. I'm absolutely fine with ignoring this patchset for the given 
reasons.


On a side note, I believe bc 1.07.1 license should be GPLv3+ & LGPLv3 
only, unless I'm missing something.


Alex and I actually discussed that in the meantime and we concluded that 
given license notices in the source itself and the description on the 
home page that it actually is only "GPLv3+". But thats just a side notice.


Thanks for the heads up!

Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/2] bc: bump version to 1.07.1

[Josef Holzmayr]

Signed-off-by: Josef Holzmayr <holzm...@rsi-elektrotechnik.de>
---
 meta/recipes-extended/bc/bc_1.06.bb| 26 
 meta/recipes-extended/bc/bc_1.07.1.bb  | 25 +++
 .../bc/files/fix-segment-fault.patch   | 28 --
 3 files changed, 25 insertions(+), 54 deletions(-)
 delete mode 100644 meta/recipes-extended/bc/bc_1.06.bb
 create mode 100644 meta/recipes-extended/bc/bc_1.07.1.bb
 delete mode 100644 meta/recipes-extended/bc/files/fix-segment-fault.patch

diff --git a/meta/recipes-extended/bc/bc_1.06.bb 
b/meta/recipes-extended/bc/bc_1.06.bb
deleted file mode 100644
index d8c8a86..000
--- a/meta/recipes-extended/bc/bc_1.06.bb
+++ /dev/null
@@ -1,26 +0,0 @@
-SUMMARY = "Arbitrary precision calculator language"
-HOMEPAGE = "http://www.gnu.org/software/bc/bc.html;
-
-LICENSE = "GPLv2+ & LGPLv2.1"
-LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
-file://COPYING.LIB;md5=d8045f3b8f929c1cb29a1e3fd737b499 \
-
file://bc/bcdefs.h;endline=31;md5=46dffdaf10a99728dd8ce358e45d46d8 \
-
file://dc/dc.h;endline=25;md5=2f9c558cdd80e31b4d904e48c2374328 \
-
file://lib/number.c;endline=31;md5=99434a0898abca7784acfd36b8191199"
-
-SECTION = "base"
-DEPENDS = "flex"
-PR = "r3"
-
-SRC_URI = "${GNU_MIRROR}/bc/bc-${PV}.tar.gz \
-   file://fix-segment-fault.patch "
-
-SRC_URI[md5sum] = "d44b5dddebd8a7a7309aea6c36fda117"
-SRC_URI[sha256sum] = 
"4ef6d9f17c3c0d92d8798e35666175ecd3d8efac4009d6457b5c99cea72c0e33"
-
-inherit autotools texinfo update-alternatives
-
-ALTERNATIVE_${PN} = "dc"
-ALTERNATIVE_PRIORITY = "100"
-
-BBCLASSEXTEND = "native"
diff --git a/meta/recipes-extended/bc/bc_1.07.1.bb 
b/meta/recipes-extended/bc/bc_1.07.1.bb
new file mode 100644
index 000..5e4bd95
--- /dev/null
+++ b/meta/recipes-extended/bc/bc_1.07.1.bb
@@ -0,0 +1,25 @@
+SUMMARY = "Arbitrary precision calculator language"
+HOMEPAGE = "http://www.gnu.org/software/bc/bc.html;
+
+LICENSE = "GPLv2 & GPLv3+ & LGPLv3"
+LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
+file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6 \
+
file://bc/bcdefs.h;endline=28;md5=1acd4c17e6f5fe1f387fd12ac7d96fe2 \
+
file://dc/dc.h;endline=22;md5=6b2786d0e2f15f966acc13f3e71f3ce0 \
+
file://lib/number.c;endline=31;md5=5c437fc63f83a46d4d769d4dd1e74525"
+
+SECTION = "base"
+DEPENDS = "flex ed-native"
+PR = "r0"
+
+SRC_URI = "${GNU_MIRROR}/bc/bc-${PV}.tar.gz"
+
+SRC_URI[md5sum] = "cda93857418655ea43590736fc3ca9fc"
+SRC_URI[sha256sum] = 
"62adfca89b0a1c0164c2cdca59ca210c1d44c3ffc46daf9931cf4942664cb02a"
+
+inherit autotools texinfo update-alternatives
+
+ALTERNATIVE_${PN} = "dc"
+ALTERNATIVE_PRIORITY = "100"
+
+BBCLASSEXTEND = "native"
diff --git a/meta/recipes-extended/bc/files/fix-segment-fault.patch 
b/meta/recipes-extended/bc/files/fix-segment-fault.patch
deleted file mode 100644
index 20c0da2..000
--- a/meta/recipes-extended/bc/files/fix-segment-fault.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-Upstream-Status: Pending
-
-when run command such as 'echo "a = 13" | bc -l', it segmentation faults.
-This patch is from 
http://www.mail-archive.com/blfs-support@linuxfromscratch.org/msg04602.html.
-
-Signed-off-by: Kai Kang <kai.k...@windriver.com>
-
 bc-1.06/lib/number.c.orig  2003-09-26 21:14:02.0 +
-+++ bc-1.06/lib/number.c   2003-09-26 21:14:26.0 +
-@@ -34,6 +34,7 @@
- #include 
- #include 
- #include 
-+#include 
- #include /* Prototypes needed for external utility routines. */
- 
- #define bc_rt_warn rt_warn
 bc-1.06/bc/load.c.orig 2003-09-26 21:14:14.0 +
-+++ bc-1.06/bc/load.c  2003-09-26 21:14:26.0 +
-@@ -156,7 +156,7 @@
-   long  label_no;
-   long  vaf_name; /* variable, array or function number. */
-   long  func;
--  program_counter save_adr;
-+  static program_counter save_adr;
- 
-   /* Initialize. */
-   str = code;
-- 
2.7.4


-- 
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/2] version bump bc to 1.07.1

[Josef Holzmayr]

This series bumps bc to version 1.07.1.

The changes include the needed:
- change of license to GPLv3 & LGPLv3 & GPLv2+
- removal of patch which has been upstreamed
- add native class to ed as it is now a build time dependency

Josef Holzmayr (2):
  ed: add native class
  bc: bump version to 1.07.1

 meta/recipes-extended/bc/bc_1.06.bb| 26 
 meta/recipes-extended/bc/bc_1.07.1.bb  | 25 +++
 .../bc/files/fix-segment-fault.patch   | 28 --
 meta/recipes-extended/ed/ed_1.14.2.bb  |  3 +++
 4 files changed, 28 insertions(+), 54 deletions(-)
 delete mode 100644 meta/recipes-extended/bc/bc_1.06.bb
 create mode 100644 meta/recipes-extended/bc/bc_1.07.1.bb
 delete mode 100644 meta/recipes-extended/bc/files/fix-segment-fault.patch

-- 
2.7.4


-- 
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/2] ed: add native class

[Josef Holzmayr]

Signed-off-by: Josef Holzmayr <holzm...@rsi-elektrotechnik.de>
---
 meta/recipes-extended/ed/ed_1.14.2.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-extended/ed/ed_1.14.2.bb 
b/meta/recipes-extended/ed/ed_1.14.2.bb
index 87d03b1..06d7cd1 100644
--- a/meta/recipes-extended/ed/ed_1.14.2.bb
+++ b/meta/recipes-extended/ed/ed_1.14.2.bb
@@ -33,3 +33,6 @@ do_install() {
rm -f ${D}${infodir}/dir
fi
 }
+
+BBCLASSEXTEND = "native"
+
-- 
2.7.4


-- 
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] OpenEmbedded Developer Meeting Oct 22, 2017 in Prague (before ELCE)

[Josef Holzmayr]

On 20.09.2017 09:50, Mike Looijmans wrote:
Depends on what I'll be able tug along in my luggage on the airplane, 
but whatever I can bring is probably suited for public display. A few 
circuit boards will certainly fit, so if the stand could provide a HDMI 
monitor (or TV) to connect them to that'd be awesome.


I can provide a rather small (7") TV with HDMI input if needed. Warning 
ahead: IIRC it has some 1368 resolution and overscan can't be switched 
off. Just let me know if I shall bring it.


Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/7] create_npm.py: convert MIT/X11 to MIT

[Josef Holzmayr]

Hi Anders,

from what I can see the problem is rooted a bit deeper, and this patch 
(together with 5, 6, 7 from the series) is basically symptomatic:
the package.jsons license field is mostly expected to be spdx-compliant 
(see https://docs.npmjs.com/files/package.json#license). So I think we 
need a concept here to actually handle the complexity it brings, or we 
end up rewriting a boatload of license strings. And doing that in 
create_npm.py just feels wrong to me.


my $.02
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [Openembedded-architecture] [PATCH] meta: start to ignore the largefile distro feature

[Josef Holzmayr]

On 07.03.2017 15:45, Burton, Ross wrote:


On 7 March 2017 at 14:43, Mark Hatle <mark.ha...@windriver.com
<mailto:mark.ha...@windriver.com>> wrote:

At this point, I'm not sure there is any reason to NOT using
largefile system
wide.  It's a common enough feature, and even 'small' devices (with
sdcard
slots) can run into large file problems now.


My thoughts exactly, fwiw.


FULLACK

--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] npm thoughts

[Josef Holzmayr]

Additional packaging/dependency thoughts:

Using the devtool mechanism to create a recipe basically packs up all 
dependencies. While this is a relatively easy solution to make sure that 
the resulting package is functional, I can see some issues:
- Dependency tracking via bitbake is virtually nonexistent. How would 
one package a npm thing to use other, already packaged dependencies?
- I see problems in the reproductibility of the builds when relying on 
npmjs as upstream server. Packages come and go there sometimes. Is there 
a way to redirect dependencies to a custom hosted mirror?
- Given the current situation, the best practise seems to be to have 
package.json take care of the needed modules, and have it handle that. 
Means in my opinion that there should be as little npm-based stuff 
installed as possible. Exactly one, in the optimal case. Downside: this 
means a second dependency tracking is layered under bitbake. No good 
that sounds


my $.02
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] npm thoughts

[Josef Holzmayr]

Hi Trevor,

On 28.02.2017 19:00, Trevor Woerner wrote:

Ideally "devtool add ..." wouldn't choke and crash when it encounters a
LICENSE string it doesn't understand. When parsing license strings from random
places on The Internet it's inevitable odd things will come up :-)


Yeah, it even seems to get very upset for rather non-obscure things like 
lodash or redux. I ran into that too and will try to have a look.


Greetz
--
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core