On Tue, Feb 22, 2022 at 1:44 PM Sudip Mukherjee
<sudip.mukherjee@...> wrote:
Hi Lukas,
On 21/02/2022 4:23 pm, Lukas Bulwahn wrote:
On Mon, Feb 21, 2022 at 4:01 PM Gabriele Paoloni <gpaoloni@...> wrote:
<snip>
As an example, we may consider collecting known issues for a few base
Debian base packages and the Linux kernel.
Right now the focus of ELISA has been the Kernel only (also due to BW
limitations) whereas here you intend to extend the scope. Correct?
That is correct. As the scope is limited to handling known issues, we
can---even with a small team---probably cover more than just the
kernel; further, the kernel development is certainly the most
challenging upstream project to look into. For the scope extension, I
basically copied the concept of "base packages" from the CIP (Civil
Infrastructure Platform) Project.
They define a "minimal core" by pointing to a few base packages in
Debian; you will probably find (different versions of) those packages
in all other Linux distributions. I just picked Debian as CIP defined
that reference and it is the most 'company-independent' distro as of
now.
Not really sure why you want to look at Debian packages. iiuc, CIP only
uses Debian as a base for their build runners. But I think the actual
image which is in the product is based on Yocto. Also, if I consider all
the automotive companies I have worked for, I have not seen anyone (yet)
who is using Debian in the car. But again, I have heard of a company
(from a Linkedin recruitment agent) who are planning to use a Debian
based image for the IVI.
Well, I think we can settle on looking at the upstream projects first.
The distributions of interest can then be considered in a second
round, among the contributors.
Yocto (in its own words) is not a distribution---so, this means that
the companies just randomly pick arbitrary versions and composition of
packages and ship it. That makes the task of even naming the known
issues almost impossible for anyone outside of the company.
Slowly I am concluding that "taking what CIP defines as core packages"
as a starting point seems to be more difficult than beneficial,
though.
Lukas
But, otoh, being a Debian Developer, I will be very happy if you look
into Debian packages. :)
--
Regards
Sudip