All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
	Romain Naour <romain.naour@gmail.com>, Bryan Brattlof <bb@ti.com>,
	Brandon Maier <brandon.maier@collins.com>,
	Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH 1/2] Revert "Create a .gitignore file in the CANONICAL_O directory"
Date: Fri, 26 Jul 2024 09:33:42 +0200	[thread overview]
Message-ID: <20240726093342.67e2aba8@windsurf> (raw)
In-Reply-To: <20240724-revert-output-gitignore-v1-1-510a2795884c@collins.com>

On Wed, 24 Jul 2024 21:23:20 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:

> The packages 'python-jsonschema-specifications', 'pydantic-core', and
> likely other packages based on Python maturin silently stopped
> installing files to the host and target directories after commit
> a14c862c08.
> 
> A similar issue was reported by the Conda project[1]. It seems some
> build tools scan for gitignore files to decide what files to build
> and install.
> 
> I attempted various combinations of gitignore patterns including
> mimicking the Conda project's gitignore[2], but the only thing that has
> worked reliably is the original `/output` ignore in the root Buildroot
> directory.
> 
> This reverts commit a14c862c08865e053d5fce90a0d0323b8f9e4bc0.
> 
> [1] https://github.com/PyO3/maturin/issues/1911
> [2] https://github.com/conda-forge/conda-smithy/blob/main/conda_smithy/feedstock_content/.gitignore
> Reported-by: Bryan Brattlof <bb@ti.com>
> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
> ---
>  .gitignore | 1 +
>  Makefile   | 3 ---
>  2 files changed, 1 insertion(+), 3 deletions(-)

Thanks, both applied. Of course, I'm not a huge fan of PATCH 2/2,
because there's really no reason for output folders to be called
"output<something>", but until we can create the .gitignore file in the
output folder itself, I guess this is a reasonable workaround to allow
people to create multiple output directories that are ignored.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-07-26  7:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 21:23 [Buildroot] [PATCH 0/2] Fix .gitignore in CANONICAL_O breaking Python packages Brandon Maier via buildroot
2024-07-24 21:23 ` [Buildroot] [PATCH 1/2] Revert "Create a .gitignore file in the CANONICAL_O directory" Brandon Maier via buildroot
2024-07-25  5:51   ` Thomas Petazzoni via buildroot
2024-07-25  6:04     ` James Hilliard
2024-07-25 15:01       ` Brandon Maier via buildroot
2024-07-25 15:17         ` James Hilliard
2024-07-25 19:34     ` Brandon Maier via buildroot
2024-07-26  9:25       ` James Hilliard
2024-07-26  7:33   ` Thomas Petazzoni via buildroot [this message]
2024-07-24 21:23 ` [Buildroot] [PATCH 2/2] gitignore: ignore multiple output directories Brandon Maier via buildroot

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=20240726093342.67e2aba8@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bb@ti.com \
    --cc=brandon.maier@collins.com \
    --cc=buildroot@bubu1.eu \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.