FS#16384 - Inconsistency of makepkg's activities in devel_check() for Mercurial
Attached to Project:
Pacman
Opened by Evgeny Burmentyev (virus_found) - Monday, 28 September 2009, 13:39 GMT
Last edited by Allan McRae (Allan) - Friday, 10 August 2012, 04:56 GMT
Opened by Evgeny Burmentyev (virus_found) - Monday, 28 September 2009, 13:39 GMT
Last edited by Allan McRae (Allan) - Friday, 10 August 2012, 04:56 GMT
|
Details
Initiated by Waldteufel in the forums
http://bbs.archlinux.org/viewtopic.php?id=78150
, look there for more info and suggestions.
$newpkgver for a Mercurial PKGBUILD is computed in a very different way in comparison with other PKGBUILDS. A repository is cloned or pulled/updated before the current revision number check. I assume, initially it was a workaround, but now there must be a way of making this in more convenient way with increasing Mercurial releases? There is a part of makepkg script attached, to show the differences in $newpkgver behaviour. STR: 1. Run makepkg on any Mercurial PKGBUILD (with _hgroot variable in it). 2. See the messages after "==> Determining latest hg revision...", makepkg pulls or clones the whole repository right now. 
makepkg_part
(1.4 KiB)
|
This task depends upon
Closed by Allan McRae (Allan)
Friday, 10 August 2012, 04:56 GMT
Reason for closing: Implemented
Additional comments about closing: https://projects.archlinux.org/pacman.gi t/commit/?id=024bc44a
Friday, 10 August 2012, 04:56 GMT
Reason for closing: Implemented
Additional comments about closing: https://projects.archlinux.org/pacman.gi t/commit/?id=024bc44a
Kind regards
Waldteufel
-
FS#13727-
FS#15895-
FS#7816I wonder if we could redesign the whole VCS system to take care of all these problems.