Package Details: fontconfig-git 2.13.1+20+g2bd559f-1

Git Clone URL: (read-only)
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
Last Packager: amoka
Votes: 7
Popularity: 0.005477
First Submitted: 2013-01-21 03:52
Last Updated: 2018-11-16 22:47

Required by (1000)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

Scimmia commented on 2013-04-24 01:44

Which makes no sense whatsoever in an AUR PKGBUILD.

yuyichao commented on 2013-04-23 21:26

To test different branches.

Scimmia commented on 2013-04-23 21:01

And why, exactly, would you ever do that in a PKGBUILD?

yuyichao commented on 2013-04-23 11:53

No. Switching branches is (relatively) simple although your way will not work both because it has to be run before pkgver() (in order to get the right pkgver) and because a simple `git checkout` is not enough when you have patches.

Yes by switch URL what I really need is switching to a branch that only exists on another URL, and neither `git checkout`, nor anything without switching remote URL, can do that.

Scimmia commented on 2013-04-23 10:56

You're making such a big deal about changing the URL, what are you talking about? Just changing where HEAD is (branch or ref)? Simple, do a "git checkout" in the prepare function. Doing it this was is a bit ridiculous, and pkgver won't even be run.

yuyichao commented on 2013-04-12 22:21

I can fix other things. But still, the main problem is makepkg cannot change the url to fetch sources from without deleting original copy (So I will not use the git url in source array unless this is fixed).

Earnest commented on 2013-04-12 22:14

It sounds like you're trying to apply patches and edit the source which makepkg has downloaded instead of in a local git directory.

At any rate here's my final (personal) PKGBUILD:

PS: Please don't use pkgbase [1] "fontconfig" (this is not a split package, nor would you use this for split packages on the AUR) and please update the maintainer field.


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.