Pacman

Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.
Tasklist

FS#39718 - [makepkg] add subfolder support for VCS sources

Attached to Project: Pacman
Opened by vicencb (vicencb) - Wednesday, 02 April 2014, 19:09 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 02 April 2014, 19:22 GMT
Task Type Feature Request
Category makepkg
Status Assigned
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.2
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

VCS sources are specified like this:
[folder::][vcs+]url[#fragment]
I'm trying to use a 'folder' like "pkg_group/pkg_xx" to store all the sources related to a package group into "${SRCDEST}/pkg_group/"
and encountered two problems:
1)
"${SRCDEST}/pkg_group/" directory is not created.
As a nasty workaround I've added "_make_dst_dir=$(mkdir -p ${SRCDEST}/pkg_group)" to the PKGBUILD
2)
In the source array there is a first BZR entry, several GIT entries and finally another BZR entry.
When makepkg is at "Extracting sources..." everything goes fine until the last source entry, which stops with the following error:
-> Creating working copy of pkg_group/pkg_xx bzr repo...
/usr/bin/makepkg: line 520: cd: pkg_group/pkg_xx: No such file or directory
==> ERROR: Failure while creating working copy of pkg_group/pkg_xx bzr repo
Aborting
I don't know why the first BZR entry works fine and the other one does not. I'll post my PKGBUILD if requested to reproduce the problem.
In any case I think a simple mkdir will solve it.

So, all in all, my feature request is to add proper support for subfolders in the VCS sources.
This task depends upon

Comment by vicencb (vicencb) - Thursday, 12 June 2014, 19:28 GMT
This patch solves both problems described above, at least for one test case.
Please, can somebody review it.
The 0.9 KiB patch is incorrect, but can't delete it.

Loading...