Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#31221 - Don’t create a working directory for hg with new vcs syntax

Attached to Project: Pacman
Opened by Link Mauve (linkmauve) - Tuesday, 21 August 2012, 10:40 GMT
Last edited by Allan McRae (Allan) - Tuesday, 18 September 2012, 14:31 GMT
Task Type Bug Report
Category makepkg
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Very Low
Priority Normal
Reported Version git
Due in Version 4.1.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Some projects can be pretty big, and creating a working directory from the hg repo waste space that will never be used.
To disable that, use `hg clone -U` instead of `hg clone`, and `hg pull` instead of `hg pull -u`.
Of course, this is only for $startdir/repo, the second clone to $srcdir/repo needs the working directory creation as it will contain the sources.

Steps to Reproduce:
Run makepkg with a -hg PKGBUILD using the new syntax.
$startdir/repo contains the full source tree, while it could only contain a .hg directory, the Mercurial repository.
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 18 September 2012, 14:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  https://projects.archlinux.org/pacman.gi t/commit/?id=800799ea
Comment by Allan McRae (Allan) - Tuesday, 21 August 2012, 10:55 GMT
That breaks "makepkg --allsource"
Comment by Allan McRae (Allan) - Tuesday, 21 August 2012, 10:58 GMT
Also, if BUILDDIR is set to a tmpfs (for building in RAM), this would require the repo gets downloaded every build.
Comment by Link Mauve (linkmauve) - Tuesday, 21 August 2012, 11:09 GMT
For --allsource, it just include only the repository, from which the working directory can be recreated by running `hg update`.

For BUILDDIR, it’s exactly the same as currently, the repo cloned from the external source will still be available if has been put in a persistent directory, only the build repo will need to be recreated each time, like currently.

Edit: I’ve noticed that git repositories include only the content of the otherwise .git directory, here it’s exactly the same except Mercurial still needs those files to be in a $reponame/.hg directory.
Comment by Allan McRae (Allan) - Tuesday, 21 August 2012, 12:01 GMT
I understand now. I was completely lead astray by the description of "hg clone -U" I found... Reading some more I now see what the request is for. I will make the patch.

Loading...