should I do create new buildroots when I install another packages?

[fideliochan]

Newbie Arch User here, I did not want to use wrappers such as yay, paru etc. so should I create buildroots with ccm u command whenever I install something from AUR?
Thanks.

[graysky2]

It's up to you. I tend to build most things in a buildroot to keep my live system free of needless depends or to make sure the makedeps in the PKGBUILD I am using are correct. Another use case for buildroots is cross compiling with distcc but that is more niche than the first two for me.

And yes, AUR helpers generally do not help and break things. Closing but feel free to continue dialog if needed.

[fideliochan]

@graysky2 It is me again :D This is tree view of my aur pkgs. I put libeb in goldendict-ng as subfolder since its aur dep, if I want to keep my system free of needled dep as u should I create buildroot per dir?

[kaguya@gnu aur]$ tree -d
.
├── auracle-git
│   └── auracle
│       ├── branches
│       ├── hooks
│       ├── info
│       ├── objects
│       │   ├── info
│       │   └── pack
│       └── refs
│           ├── heads
│           └── tags
├── clean-chroot-manager
└── goldendict-ng
    └── libeb

Also what should I do in situation like goldendict-ng's? should I do cd goldendict-ng/libeb and ccm u s a and do cd .. ccm u s ?
Thank you so much for this beauty.

[graysky2]

I don't understand your directory question. You do not need to order them. If foo requires bar to build, you just need to build bar first and then build foo. The dir tree does not matter.

[fideliochan]

Ah, then should I add bar to local repo if both of them aur pkg?

[graysky2]

Yes, or just build bar with ccm then build foo with ccm. It does it automatically.