Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/netopeer2: set SYSREPO_SHM_PREFIX and cleanup shm files after installation
Date: Thu, 11 Feb 2021 19:39:22 +0100	[thread overview]
Message-ID: <20210211183922.GI1679218@scaer> (raw)
In-Reply-To: <e3a208c6-a577-4057-8c42-fbdf9f0c2196@cesnet.cz>

Jan, All,

On 2021-02-11 14:56 +0100, Jan Kundr?t spake thusly:
> On ned?le 7. ?nora 2021 12:39:46 CET, Peter Seiderer wrote:
> >Still the question, are the shm files needed at runtime? If so they should
> >belong in the target directory (or created by a startup script), of not why
> >create them at first (why not skip the setup.sh/sysrepoctl step)? Are there
> >any other products/output of the setup.sh/sysrepoctl step?
> >
> >The setup.sh is called with the following environment variables:
> >
> >	NP2_MODULE_DIR /usr/share/yang/modules/netopeer2
> >	NP2_MODULE_PERMS 600
> >	NP2_MODULE_OWNER seiderer
> >	NP2_MODULE_GROUP users
> >
> >A (quick) strace check of setup.sh run shows no other output than the shm
> >files...
> 
> Disclaimer: While I work for the same company as the sysrepo+netopeer2
> maintainers, I'm not upstream. On the other hand, we've been using
> sysrepo+netopeer2 on ARM via Buildroot for a few years. Here's what we're
> doing. Our use case is having a common buildroot build image for several
> appliances that each use a slightly different set of YANG modules. We also
> have a read-only rootfs, with a separate partitions for stateful data, and
> we're using the A/B boot slots via RAUC.

Thank you for these extensive explanations; very interesting! ?

I eventually decided to apply the patch from Heiko, because it does fix
an issue we have currently.

Also, even though your experience suggests not installing things at build
time, but only at run time (and I have no argument against that), I
believe Heiko is actually using netopeer2, and that the way it is packaged
in Buildroot at least works for him, in his very particular case.

So, even if what we have now is not perfect, it seems to work
well-enough to be usable, especially now that we can avoid conflicts
when installing the YANG modules at build/install time.

Again, thank you very much for your extensive and very valuable feedback!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2021-02-11 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 10:57 [Buildroot] [PATCH 1/2] package/netopeer2: set SYSREPO_SHM_PREFIX and cleanup shm files after installation Heiko Thiery
2021-02-06 10:57 ` [Buildroot] [PATCH 2/2] package/netopeer2: add dependency to host-sysrepo Heiko Thiery
2021-02-06 11:35 ` [Buildroot] [PATCH 1/2] package/netopeer2: set SYSREPO_SHM_PREFIX and cleanup shm files after installation Yann E. MORIN
2021-02-07 11:39 ` Peter Seiderer
2021-02-07 21:21   ` Heiko Thiery
2021-02-07 22:56     ` Peter Seiderer
2021-02-11 13:56   ` Jan Kundrát
2021-02-11 18:39     ` Yann E. MORIN [this message]
2021-02-11 20:58     ` Heiko Thiery
2021-02-11 18:32 ` Yann E. MORIN

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=20210211183922.GI1679218@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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