From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@uclibc.org
Subject: Re: [Buildroot] downloads: removing git repos and offline builds
Date: Wed, 20 Nov 2024 13:25:29 -0000 (UTC) [thread overview]
Message-ID: <vhko09$a5m$1@ciao.gmane.io> (raw)
In-Reply-To: eb63a9dac0a90b6aa67315f285039615__24185.6297756144$1732095375$gmane$org@umbiko.net
On 2024-11-20, Andreas Ziegler <br015@umbiko.net> wrote:
> On 2024-11-19 16:12, Grant Edwards wrote:
>
>> [...] A question has come up with opkg-utils. It downloads a
>> source tarball and clones a git repository:
>> [...]
>> Actually, I'm not entirely sure whether it downloaded that tarball or
>> created it from the git repository -- I now suspect the latter.
>
> The order is git repository -> tarball -> build directory. The git
> repository will be reused or recreated if either the package version
> changes or the tarball is removed. I use this behaviour occasionally
> to 'fake' package versions.
Thanks for confirming that.
>> [....] Requiring offline builds for production firmware can't be
>> that unusual.
>>
>> Is just removing the git repo and archiving the tarball how people
>> usually deal with this situation?
>
> Any objections to just using a line in .gitignore?
>
> downloads/*/git
Not really, that should work fine. I initially decided to remove it
just to be sure whether or not it actually needed to be there to do a
build.
--
Grant
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-11-20 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.17954.1732090118.1448558.buildroot@buildroot.org>
2024-11-20 9:27 ` [Buildroot] downloads: removing git repos and offline builds Andreas Ziegler
[not found] ` <eb63a9dac0a90b6aa67315f285039615__24185.6297756144$1732095375$gmane$org@umbiko.net>
2024-11-20 13:25 ` Grant Edwards [this message]
2024-11-19 16:12 Grant Edwards
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='vhko09$a5m$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@uclibc.org \
/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