Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#78602 - pkgctl-repo-clone needs --depth option to clone of current package without git-history

Attached to Project: Arch Linux
Opened by David C. Rankin (drankinatty) - Thursday, 25 May 2023, 06:38 GMT
Last edited by Toolybird (Toolybird) - Thursday, 25 May 2023, 07:51 GMT
Task Type Feature Request
Category Arch Projects
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



pkgctl-repo-clone needs a --depth option (like `asp export pgkname`)

Per the tread on lists.archlinux "Is there "depth" control for pkgctl-repo-clone like "asp export" to get only the latest commit?", pkgctl-repo-clone needs a --depth option so it behaves like `asp export` allowing the fetch of the current package files only. If you are simply building the current package, then there is no need for the full clone with git-history (which can be very significant for large long-lived packages). This will also save bandwidth and costs for Arch.

It would be fine to simply pass the '--depth X' option through to git. It would be very convenient to add an `-e --export` that would just pull the current PKGBUILD and current files without any git history at all (a true equivalent to `asp export pkgname`)
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 25 May 2023, 07:51 GMT
Reason for closing:  None
Additional comments about closing:  @gromit "feature request have to be opened on the gitlab project, as the user has also already been told on the ML"
Comment by Toolybird (Toolybird) - Thursday, 25 May 2023, 06:53 GMT
Thanks, but devtools issues now live in Arch's GitLab instance [1]. Could you please re-submit your issue there?