All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Maier via buildroot <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Brandon Maier via buildroot" <buildroot@buildroot.org>
Cc: "Ricardo Martincoski" <ricardo.martincoski@datacom.com.br>
Subject: Re: [Buildroot] [PATCH v2 3/3] docs/manual/adding-packages-tips: mention uv
Date: Mon, 28 Oct 2024 13:53:44 +0000	[thread overview]
Message-ID: <D57HN0FMMQD5.CLENQUA9Q7LB@collins.com> (raw)
In-Reply-To: <20241026134400.3621f46b@windsurf>

Hi Thomas,

On Sat Oct 26, 2024 at 11:44 AM UTC, Thomas Petazzoni via buildroot wrote:
> On Wed, 09 Oct 2024 14:14:58 +0000
> Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
>
> > +----
> > +$ uv run -s ./utils/check-package
> > +----
>
> -s doesn't exist here:
>
> 🐧  uv run -s ./utils/check-package
> error: unexpected argument '-s' found
>
> Usage: uv run [OPTIONS] <COMMAND>
>
> For more information, try '--help'.
>
> I have:
>
> 🐧  uv --version
> uv 0.4.10

I call this out in the patch documentation, `uv` version 0.4.19 or later
is required. The '-s' flag was added only recently.

The other option would be to rename `./utils/check-package` to have the
'.py' extension. The '-s' is only required to tell `uv` it's a Python
script.

Thanks for reviewing my series!
Brandon
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-10-28 13:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 14:14 [Buildroot] [PATCH v2 0/3] utils/check-package: make check-package easier to run Brandon Maier via buildroot
2024-10-09 14:14 ` [Buildroot] [PATCH v2 1/3] docs/manual/adding-packages-tips: mention check-package requirements Brandon Maier via buildroot
2024-10-26 11:40   ` Thomas Petazzoni via buildroot
2024-11-11 10:31     ` Peter Korsgaard
2024-10-09 14:14 ` [Buildroot] [PATCH v2 2/3] utils/check-package: add inline script requirements Brandon Maier via buildroot
2024-10-26 11:41   ` Thomas Petazzoni via buildroot
2024-11-11 10:31     ` Peter Korsgaard
2024-10-09 14:14 ` [Buildroot] [PATCH v2 3/3] docs/manual/adding-packages-tips: mention uv Brandon Maier via buildroot
2024-10-26 11:44   ` Thomas Petazzoni via buildroot
2024-10-28 13:53     ` Brandon Maier 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=D57HN0FMMQD5.CLENQUA9Q7LB@collins.com \
    --to=buildroot@buildroot.org \
    --cc=brandon.maier@collins.com \
    --cc=ricardo.martincoski@datacom.com.br \
    --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.