Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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/libtevent: add libtevent package
Date: Thu, 24 Oct 2024 16:13:24 +0200	[thread overview]
Message-ID: <20241024161324.086d8f3b@windsurf> (raw)
In-Reply-To: <VI1PR06MB89264486CFDAE541386E7431AD4E2@VI1PR06MB8926.eurprd06.prod.outlook.com>

Hello Ayrton,

(Thanks for your feedback. A good practice is to strip the parts of the
e-mail you're not replying to. See below how I did it. Also your e-mail
client doesn't seem to wrap lines properly.)

On Thu, 24 Oct 2024 09:04:27 +0000
Ayrton Leyssens <aleyssens@idtech.be> wrote:

> > This whole file looks exactly identical to libtalloc. Is everything
> > exactly identical, and needed for libtevent as well, or did you
> > just copy/paste? :-)  
>
> Indeed, mostly copy paste.
> Since both use the waf-package system and the sources come from
> samba, they are quite identical.

Quite identical, or fully identical? Basically, I'd like to make sure
libtevent.mk is not more complicated than it needs to be. Is everything
you've added in libtevent.mk actually needed to allow building
libtevent?

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

  reply	other threads:[~2024-10-24 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 11:46 [Buildroot] [PATCH 1/1] package/libtevent: add libtevent package Ayrton Leyssens
2024-10-23 20:30 ` Thomas Petazzoni via buildroot
2024-10-24  9:04   ` Ayrton Leyssens
2024-10-24 14:13     ` Thomas Petazzoni via buildroot [this message]
2024-10-24 14:27       ` Ayrton Leyssens

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=20241024161324.086d8f3b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox