From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Ayrton Leyssens <aleyssens@idtech.be>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/certmonger: add certmonger package
Date: Tue, 29 Oct 2024 19:23:17 +0100 [thread overview]
Message-ID: <20241029192317.4163496b@windsurf> (raw)
In-Reply-To: <VI1PR06MB8926480FA28C325114C6C20CAD4E2@VI1PR06MB8926.eurprd06.prod.outlook.com>
Hello Ayrton,
On Thu, 24 Oct 2024 10:14:04 +0000
Ayrton Leyssens <aleyssens@idtech.be> wrote:
> > Also, are you sure all those dependencies are mandatory dependencies, i.e certmonger cannot be built without them?
>
> Unfortunately, yes.
> Like you said, Certmonger is quite a complex package and has a lot of dependencies.
> It might be possible to make 'sub-selections' but this should be something implemented by the Certmonger developers.
> I am just the messenger adding the package to Buildroot.
Sure, if those dependencies are mandatory, they are, and the Buildroot
package should reflect that. Since they were really numerous, I thought
I would ask to make sure you had looked into this carefully.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-29 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 11:56 [Buildroot] [PATCH 1/1] package/certmonger: add certmonger package Ayrton Leyssens
2024-10-23 20:55 ` Thomas Petazzoni via buildroot
2024-10-24 10:14 ` Ayrton Leyssens
2024-10-29 18:23 ` Thomas Petazzoni via buildroot [this message]
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=20241029192317.4163496b@windsurf \
--to=buildroot@buildroot.org \
--cc=aleyssens@idtech.be \
--cc=thomas.petazzoni@bootlin.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.