Package Details: fontconfig-git 2.13.91+18+g01e4f08-1

Git Clone URL: (read-only, click to copy)
Package Base: fontconfig-git
Description: A library for configuring and customizing font access (from git)
Upstream URL:
Licenses: custom
Conflicts: fontconfig
Provides: fontconfig
Submitter: yuyichao
Maintainer: amoka (shoober420)
Last Packager: amoka
Votes: 9
Popularity: 0.50
First Submitted: 2013-01-21 03:52
Last Updated: 2019-12-18 19:10

Required by (1000)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3

yuyichao commented on 2013-04-12 20:54

If I change the url without deleting the cache, makepkg will complain about it is not a clone of the repository.

There is nothing to do with prepare, I am talking about resetting before fetching (and I am not sure if makepkg cannot do this, although it is very likely that it cannot).

`git reset` is for resetting current work directory to a commit so that git will not complaining about uncommit change due ty patches.

`git clean` is for removing possible files introducing by patches (or the patch will fail). It is also very helpful to clean up build files no matter which build system the package is using, especially for build system like autotool where out-of-source build are always problematic and make clean/distclean may not enough.

For pkgver(), I will try to figure out one scheme to use later. But since makepkg cannot automatically fetch the source for me and therefore I will have to do that myself, that's not my priority.

Earnest commented on 2013-04-12 20:25

There is nothing preventing you from using `git --reset' in the `build()' function.

You should use the `prepare()' function for patches.

Also please don't use the date for the `pkgver()' as it is next to useless and should only be used if there are no other alternatives.

PS: I don't understand why you're doing `git --reset' or `git -fdx' either.

yuyichao commented on 2013-04-12 14:30

And I am also not sure if makepkg support reset before fetching either, which is necessary for packages with patches.

yuyichao commented on 2013-04-12 14:27

No I mean changing url/branch/ref in PKGBUILD without removing srcdir of a previous build.

Earnest commented on 2013-04-12 14:24

I'm sorry, what exactly do you mean by "url switch"?

Are you referring to branches? If that's the case you can use branches (fragments) by simply appending `#branch=<foobar>' to the source url.

yuyichao commented on 2013-04-12 01:53

I will NOT use the "new" cvs downloading method provided in pacman 4.1 since it doesn't support features like switch url. I am uploading a new PKGBUILD to fix the regression of updating package version though.

Earnest commented on 2013-04-11 22:40

pacman 4.1 updated PKGBUILD: