Arch Linux

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,673

Website

Possible to see the dir tree of a makepkg git cloned repo? [solved]

When makepkg clones a git repo is it possible to see the file structure of that git repo as if I cloned it?  For example, I built linux-firmware-git from the AUR.  When I enter the repo makepkg cloned, I see:

% ls
branches  hooks  info  objects  refs  HEAD  config  description  packed-refs

If I clone the source repo (eg
git clone https://git.kernel.org/pub/scm/linux/ke … mware.git), I see the dirtree git is managing.  Output of the below is truncated:

$ ls
3com                                        LICENCE.via_vt6656                 iwlwifi-bz-b0-gf-a0-92.ucode
acenic                                      LICENCE.wl1251                     iwlwifi-bz-b0-gf-a0-94.ucode
adaptec                                     LICENCE.xc4000                     iwlwifi-bz-b0-gf-a0.pnvm
...

Last edited by graysky (2025-01-09 13:14:59)

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

gromit

Package Maintainer (PM)

From: Germany

Registered: 2024-02-10

Posts: 868

Website

Re: Possible to see the dir tree of a makepkg git cloned repo? [solved]

makepkg clones the repo as bare repo, you therefore most easily need to create a clone from the bare repo:

$ git clone --bare https://gitlab.archlinux.org/archlinux/devtools.git
$ cd devtools.git
$ ls 
branches  config  description  HEAD  hooks  info  objects  packed-refs  refs
$ cd ..
$ git clone devtools.git devtools
$ cd devtools
$ ls
cliff.toml  config  contrib  doc  LICENSE  Makefile  README.md  src  test

Which underlying problem are you trying to solve?

Last edited by gromit (2025-01-09 13:10:07)

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,673

Website

Re: Possible to see the dir tree of a makepkg git cloned repo? [solved]

Thanks for the reply, gromit.  Just wondering if it is possible to see the files from makepkg's clone to avoid having to clone the repo myself if that makes sense.  I was unaware of the --bare option but found that I can see the working files from a --bare clone

git ls-tree -r --name-only HEAD
git ls-tree -r HEAD

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs