FS#16872 - the way VCS packages are handled is a mess
Attached to Project:
Pacman
Opened by Rogutės (rogutes) - Wednesday, 28 October 2009, 01:26 GMT
Last edited by Allan McRae (Allan) - Friday, 10 August 2012, 04:54 GMT
Opened by Rogutės (rogutes) - Wednesday, 28 October 2009, 01:26 GMT
Last edited by Allan McRae (Allan) - Friday, 10 August 2012, 04:54 GMT
|
Details
* Different VCS systems are handled differently. The sources
are fetched/updated automatically only for hg (if $_hgroot
and $_hgrepo are defined) and not the other VCSs. For bzr
and svn, only the revision is fetched. For cvs and darcs,
the remote repository is not contacted at all. This
incosistency is confusing.
* VCS sources should be handled before build(), like the other sources in the $source array or there should be a prepare_sources() function (which could also be useful for patching..). * VCS sources should land in $SRCDEST and not under $srcdir. |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 10 August 2012, 04:54 GMT
Reason for closing: Implemented
Additional comments about closing: https://projects.archlinux.org/pacman.gi t/commit/?id=024bc44a
Friday, 10 August 2012, 04:54 GMT
Reason for closing: Implemented
Additional comments about closing: https://projects.archlinux.org/pacman.gi t/commit/?id=024bc44a
(also check out the 4 other bug reports : http://bugs.archlinux.org/task/16384#comment50310)
I have another very annoying one related to the first point here : afaik forcever only works for cvs/svn.
It does not seem trivial at all how to handle completely different VCS system in a consistent and unified way. This will probably require some brainstorming.
Then we need to agree on how to fix all these problems, and implement the solutions..