Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@uclibc.org
Subject: [Buildroot] downloads: removing git repos and offline builds
Date: Tue, 19 Nov 2024 16:12:05 -0000 (UTC)	[thread overview]
Message-ID: <vhidcl$8c5$1@ciao.gmane.io> (raw)

I've been using buildroot for many years and have always been able to
archive (previously in SVN, now in Git/LFS) the contents of the
downloads directory so that production firmware can be built offline
using nothing but files checked out from SVN/Git.  A question has come
up with opkg-utils.  It downloads a source tarball and clones a git
repository:

    $ ls -l downloads/opkg-utils/
    total 48
    drwxr-xr-x 4 grante grante  4096 Nov 19 09:25 git
    -rw-r--r-- 1 grante grante   512 Nov 19 09:25 git.readme
    -rw-r--r-- 1 grante grante 36872 Nov 19 09:25 opkg-utils-0.6.2-br1.tar.gz

Actually, I'm not entirely sure whether it downloaded that tarball or
created it from the git repository -- I now suspect the latter.

In either case, I can't archive a git repository.

It _appears_ that removing the git repo and leaving the tar.gz file is
sufficient for doing a build, and if that tarball is present buildroot
won't need to access the upstream git repository (thus allowing
offline builds using the arhcived tarball).

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?

--
Grant

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-11-19 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 16:12 Grant Edwards [this message]
     [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

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='vhidcl$8c5$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