All of lore.kernel.org
 help / color / mirror / Atom feed
From: laurence.urhegyi@codethink.co.uk (Laurence Urhegyi)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [cip-core] RFC: Process to decide supported package list
Date: Thu, 02 May 2019 19:18:22 +0100	[thread overview]
Message-ID: <ce12a60d5f0ccf3a81ec28c856fbfb0a@codethink.co.uk> (raw)
In-Reply-To: <16205208.VlgFrJl6Ko@linux-3zh6>

Hi all,

The list attached to the below mail has been reviewed internally at 
Codethink: no strong opinions from us.

Kind regards,
Laurence


> ----------  Forwarded Message  ----------
> 
> Subject: [cip-dev] [cip-core] RFC: Process to decide supported package 
> list
> Date: Tuesday, 16 April 2019, 15:22:00 CEST
> From: kazuhiro3.hayashi at toshiba.co.jp
> To: cip-dev at lists.cip-project.org
> 
> Hello CIP developers,
> 
> I would like to suggest an idea about the process to determine the 
> package
> list that should be supported by CIP.
> It's difficult to discuss adding any packages including their 
> dependencies
> from whole Debian, mixing the two profiles.
> 
> As the first step, it would be better to start from the source package 
> list
> which binary packages are installed by debootstrap minbase.
> I attached the source package list, where only 58 packages exist.
> I guess that it's easier to discuss which packages should be supported 
> from
> such core components.
> 
> NOTE: busybox is not included in the attached list, but it have to be
> supported
> not only for the tiny profile but also initramfs (and Debian 
> installer?) in
> the generic profile.
> 
> Regarding the tiny profile, we need to keep discussion about which 
> busybox
> applet should be supported.
> I think this process should be done independently from the above 
> discussion
> because
> the all packages selected from debootstrap in the first step should be
> supported in the tiny profile as well.
> 
> Regarding voting, I have the same opinion that Daniel proposed 
> previously.
> 	1. Send an initial list and vote (>50% means accepted)
> 	2. After that, each package will be voted (>50% means accepted)
> 
> As the second step, we consider adding other packages not included in 
> the list
> one by one.
> We need to decide the detailed process of the second step later.
> 
> If you have any other opinions, please let me know.
> 
> Kind regards,
> Kazu
> 
>  Kazuhiro Hayashi
>  Corporate Software Engineering & Technology Center
>  Toshiba Corporation
>  Tel: +81-44-549-2476
>  E-mail: kazuhiro3.hayashi at toshiba.co.jp
> 
> 
> -----------------------------------------

       reply	other threads:[~2019-05-02 18:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16205208.VlgFrJl6Ko@linux-3zh6>
2019-05-02 18:18 ` Laurence Urhegyi [this message]
2019-05-28 12:27 [cip-dev] [cip-core] RFC: Process to decide supported package list kazuhiro3.hayashi at toshiba.co.jp
  -- strict thread matches above, loose matches on Subject: below --
2019-04-16 13:22 kazuhiro3.hayashi at toshiba.co.jp
2019-04-22  2:29 ` SZ Lin (林上智)
2019-04-22  3:05   ` Kento Yoshida
2019-04-24  6:47     ` SZ Lin (林上智)
2019-04-24  0:58 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-04-24  9:30 ` Pavel Machek
2019-04-24 23:57   ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-04-24 23:52 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-05-10  6:36 ` kazuhiro3.hayashi at toshiba.co.jp

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=ce12a60d5f0ccf3a81ec28c856fbfb0a@codethink.co.uk \
    --to=laurence.urhegyi@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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.