Package Details: pacman-git 6.1.0.r15.g01e64e8b-1

Git Clone URL: https://aur.archlinux.org/pacman-git.git (read-only, click to copy)
Package Base: pacman-git
Description: A library-based package manager with dependency support
Upstream URL: https://www.archlinux.org/pacman/
Licenses: GPL-2.0-or-later
Conflicts: pacman
Provides: pacman
Submitter: None
Maintainer: eclairevoyant
Last Packager: eclairevoyant
Votes: 27
Popularity: 0.000000
First Submitted: 2009-09-07 17:32 (UTC)
Last Updated: 2024-04-01 21:09 (UTC)

Required by (284)

Sources (5)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

abandonedaccount commented on 2014-09-07 18:06 (UTC)

Looks like noextract option inside PKGBUILD prevents that file from being softlinked into ${srcdir} and thus the need to use ${SRCDEST} to access it. As an example of this try chromium-dev package. Tested with: Pacman v4.1.2-406-g3e19-dirty - libalpm v8.0.2 Without noextract it is symlinked, with noextract it isn't.

rafaelff commented on 2013-04-01 07:26 (UTC)

Pacman 4.1.0 in [testing] since today.

graysky commented on 2013-03-31 19:42 (UTC)

@maggie: I believe Allan was targeting the Easter weekend for 4.1's release but likely to [testing]. I took a stab at a PKGBUILD for pacman-git that will work with the current 4.0.3 series: https://gist.github.com/graysky2/5281746 Dave - feel free to check my math :p

graysky commented on 2013-03-31 15:05 (UTC)

@j - That needs to be captured in the PKGBUILD somehow, versioned dependency or at the very least, a comment.

rafaelff commented on 2013-03-31 14:24 (UTC)

@graysky: May I guess? 1) This is AUR and a GIT PKGBUILD is development-based; 2) Once you install pacman-git, eventual PKGBUILD updates will require the current format, otherwise will fail; -- anyway, one just have to follow the migration task using Allan's pkg tarball and it is all done.

graysky commented on 2013-03-31 14:07 (UTC)

@dave - why would you post a PKGBUILD that depends on development software to the AUR if what the previous poster said is true?

rafaelff commented on 2013-03-31 12:43 (UTC)

@maggie: Are you trying to install this package with pacman 4.0.3 ? I had this problem too and @RunningDroid's answer helped me - you need 4.1.0rc installed to support urls from VCS, like GIT.

maggie commented on 2013-03-31 11:28 (UTC)

I get errors when building: ==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace. When I change the pkgver to remove the -32: ==> ERROR: There is no agent set up to handle git URLs. Check /etc/makepkg.conf.

maggie commented on 2013-03-31 11:01 (UTC)

@falconindy Can you please make this package build latest git rather than point to a static tarball? I do not know enough about it to do it myself. Your commands are different from standard git packages. Thank you.

RunningDroid commented on 2013-03-20 17:20 (UTC)

@josephgbr You should use one of the packages here to add the features you need to install pacman-git: http://allanmcrae.com/2013/03/pacman-4-1-0rc1/ @falconindy Can you add fakechroot as a checkdepends, enough tests fail without it that makepkg --check fails.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »