All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH 0/3] portable services: another use case of BR
Date: Tue, 23 Aug 2022 18:46:11 +0200	[thread overview]
Message-ID: <20220823164611.GI2167049@scaer> (raw)
In-Reply-To: <20220221043034.2736010-1-francois.perrad@gadz.org>

François, All,

On 2022-02-21 05:30 +0100, Francois Perrad spake thusly:
> This series allows to build a rootfs suitable for portable services with systemd.
> 
> A new value of "Init system" is introduced : BR2_INIT_PORTABLE.
> BR2_INIT_PORTABLE is like BR2_INIT_NONE, but with all FOO_INSTALL_INIT_SYSTEMD executed.
> 
> A new type of skeleton is required : BR2_PACKAGE_SKELETON_INIT_PORTABLE.
> 
> see https://systemd.io/PORTABLE_SERVICES/

Given the feedback on this series, and after discussing with the other
maintainers, I've now marked this series as rejected. Sorry for that.

If you believe the use-case is really important, we can reconsider it in
the light of a newer and more complete series that addresses the issues
that were raised in this review.

Thank you!

Regards,
Yann E. MORIN.

> Francois Perrad (3):
>   package/skeleton-init-portable: new skeleton
>   portable: new init system
>   portable: tweak some default values
> 
>  DEVELOPERS                                    |  1 +
>  fs/squashfs/Config.in                         |  1 +
>  package/Config.in                             |  1 +
>  package/ifupdown-scripts/Config.in            |  2 +-
>  package/pkg-generic.mk                        |  2 ++
>  package/skeleton-init-portable/Config.in      |  7 ++++++
>  .../skeleton-init-portable.mk                 | 23 +++++++++++++++++++
>  system/Config.in                              | 18 +++++++++++----
>  8 files changed, 50 insertions(+), 5 deletions(-)
>  create mode 100644 package/skeleton-init-portable/Config.in
>  create mode 100644 package/skeleton-init-portable/skeleton-init-portable.mk
> 
> -- 
> 2.32.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-08-23 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21  4:30 [Buildroot] [PATCH 0/3] portable services: another use case of BR Francois Perrad
2022-02-21  4:30 ` [Buildroot] [PATCH 1/3] package/skeleton-init-portable: new skeleton Francois Perrad
2022-02-21  4:30 ` [Buildroot] [PATCH 2/3] portable: new init system Francois Perrad
2022-02-21  4:30 ` [Buildroot] [PATCH 3/3] portable: tweak some default values Francois Perrad
2022-08-21 21:17 ` [Buildroot] [PATCH 0/3] portable services: another use case of BR Yann E. MORIN
2022-08-22 21:24   ` Yann E. MORIN
2022-08-23 16:14     ` Arnout Vandecappelle
2022-08-23 16:46 ` Yann E. MORIN [this message]
2022-08-23 18:02   ` François Perrad

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=20220823164611.GI2167049@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    --cc=fperrad@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 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.