FS#32620 - Add support for calling repo-add from makepkg

Attached to Project: Pacman
Opened by Allan McRae (Allan) - Tuesday, 13 November 2012, 03:25 GMT
Task Type Bug Report
Category makepkg
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version 4.0.3
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

[tracking patch submitted prior to patchqueue]

From: https://mailman.archlinux.org/pipermail/pacman-dev/2011-June/013339.html

I recently started playing with repo-add to build a custom repo. I
have a netbook and would like to avoid building packages directly on
the machine. However I missed the niceness of automatic install with
makepkg's -i flag. I have attempted to recreate this support for repo
management by adding an -a/--repoadd flag which, instead of using
pacman to install the package, adds it to a repo.

In order for this to work REPO_PATH and REPO_DB need to be set in
makepkg.conf, REPO_PATH being the path of the repository and REPO_DB
being the location of the database inside REPO_PATH.

I have only recently started playing with repo-add and I admit I'm not
very confident with my code. If there is any interest upstream for
this functionality, I'm willing to put in the time to perfect this
patch if someone can point me in the right direction.
This task depends upon

Comment by Eli Schwartz (eschwartz) - Tuesday, 26 November 2019, 04:52 GMT
From the list review: https://lists.archlinux.org/pipermail/pacman-dev/2011-June/013606.html

Allan would prefer a --repo-add /path/to/repo.db.tar.gz option instead of coding this into makepkg.conf, but I'm wondering... we do support PKGDEST, and it seems like this feature would have lots of synergy with that, especially since you sort of need the package to be stored in the same directory as the database.

Alternatively, and this is a big alternatively, now that makepkg has --packagelist, it is trivial to acquire the list of artifacts and copy them over yourself with a bit of scripting. Do we want this integrated into makepkg, or do we want to leave it up to automation tools operating one level up?

Loading...