grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Leo Sandoval via Grub-devel <grub-devel@gnu.org>
To: grub-devel@gnu.org
Cc: Leo Sandoval <lsandova@redhat.com>
Subject: [PATCH] Create a Containerfile with required grub packages for development
Date: Mon,  9 Jun 2025 13:20:47 -0600	[thread overview]
Message-ID: <20250609192047.2323257-1-lsandova@redhat.com> (raw)

Containers bring the ability to have ready-to-use environments and in
this case a complete Fedora container file is described containing
all required packages for building and testing grub2.

Once users manually build it, they can run the container jump into a
setup ready for development. On the other hand, if users
prefer to use bare metal instead of a containerized environment, it is
still useful to have a file explicitly indicating the required packages.
---
 container/Containerfile | 54 +++++++++++++++++++++++++++++++++++++++++
 container/README        | 14 +++++++++++
 2 files changed, 68 insertions(+)
 create mode 100644 container/Containerfile
 create mode 100644 container/README

diff --git a/container/Containerfile b/container/Containerfile
new file mode 100644
index 0000000000..dd066a2ce1
--- /dev/null
+++ b/container/Containerfile
@@ -0,0 +1,54 @@
+FROM registry.fedoraproject.org/fedora
+
+# Install required packages
+RUN dnf update -y && \
+    dnf install -y \
+        attr \
+        autoconf \
+        automake \
+        autopoint \
+        bison \
+        btrfs-progs \
+        cpio \
+        cryptsetup \
+        dosfstools \
+        e2fsprogs \
+        edk2-ovmf \
+        edk2-ovmf-ia32 \
+        erofs-utils \
+        exfatprogs \
+        f2fs-tools \
+        flex \
+        gawk \
+        gettext \
+        genromfs \
+        git \
+        hfsplus-tools \
+        jfsutils \
+        libtool \
+        lzop \
+        make \
+        mtools \
+        nilfs-utils \
+        ntfsprogs \
+        parted \
+        patch \
+        pkg-config \
+        python3 \
+        qemu-system-x86 \
+        squashfs-tools \
+        swtpm-tools \
+        tpm2-tools \
+        udftools \
+        unifont \
+        unifont-fonts \
+        which \
+        words \
+        xfsprogs \
+        xorriso \
+        zfs-fuse
+
+# clone tip of grub repository
+RUN git clone --depth 1 https://https.git.savannah.gnu.org/git/grub.git /grub
+
+WORKDIR /grub
\ No newline at end of file
diff --git a/container/README b/container/README
new file mode 100644
index 0000000000..788992abb9
--- /dev/null
+++ b/container/README
@@ -0,0 +1,14 @@
+install `podman` on your favorite distro then build it with
+
+$ podman build --tag grub .
+
+once built, you can run/launch it
+
+$ podman run -it grub
+
+and execute the standard build/test commands inside it
+
+# ./bootstrap
+# ./configure
+# ./make
+# ./make check
\ No newline at end of file
-- 
2.48.1


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

             reply	other threads:[~2025-06-09 19:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 19:20 Leo Sandoval via Grub-devel [this message]
2025-06-10  2:43 ` [PATCH] Create a Containerfile with required grub packages for development Andrew Hamilton
2025-06-14  9:06 ` Neal Gompa
2025-06-14  9:38 ` Vladimir 'phcoder' Serbinenko
2025-06-16 16:34   ` Leo Sandoval via Grub-devel
2025-06-18 14:01     ` Andrew Hamilton
2025-06-18 14:36       ` Leo Sandoval via Grub-devel

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=20250609192047.2323257-1-lsandova@redhat.com \
    --to=grub-devel@gnu.org \
    --cc=lsandova@redhat.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;
as well as URLs for NNTP newsgroup(s).