Package Details: fontconfig-git 2.13.96-1

Git Clone URL: (read-only, click to copy)
Package Base: fontconfig-git
Description: Library for configuring and customizing font access (from git)
Upstream URL:
Licenses: custom
Conflicts: fontconfig, fontconfig-docs
Provides: fontconfig, fontconfig-docs,
Replaces: fontconfig-docs
Submitter: yuyichao
Maintainer: amoka
Last Packager: amoka
Votes: 10
Popularity: 0.000002
First Submitted: 2013-01-21 03:52 (UTC)
Last Updated: 2022-02-05 16:04 (UTC)

Required by (1205)

Sources (4)

Latest Comments

shoober420 commented on 2019-08-08 16:28 (UTC)

Thanks Amoka

amoka commented on 2019-08-08 16:18 (UTC)

@shoober420 I have just added you as co-maintainer.

shoober420 commented on 2019-08-03 01:13 (UTC)

Hey amoka, would it be possible if I can co-maintain this? I've recently became interested in this package again. I'm in the process of creating a lib32-fontconfig-git at the moment.

shoober420 commented on 2018-11-14 02:38 (UTC)

I’m disowning this. I have no priority for development fontconfig builds. Anyone can feel free to maintain this. My last update is still very good.

shoober420 commented on 2018-11-02 04:44 (UTC)

Finally got the hang of this. First package upload, and its legit using the template from the main repository. Compile and enjoy. Some of us got a thing to have the latest development packages, especially when you do alot of gaming.

shoober420 commented on 2017-05-26 18:44 (UTC) (edited on 2017-05-26 18:45 (UTC) by shoober420)

I'm going to install Arch on a laptop I have, and use that as my package maintaining machine. I personally don't want ssh on my main computer. This will take a little time.

toropisco commented on 2017-05-24 23:17 (UTC)

A quick note: I hope you are referring to adding lib32- support. I never got around to it. $CARCH=i686 is not worth supporting anymore as it is officially unsupported as of September. If there is a community effort to continue onwards, anyone who wants such binary can edit the PKGBUILD him/herself.

toropisco commented on 2017-05-24 22:09 (UTC)

@shoober420 you are welcome to maintain the package. I'm taking the appropriate steps after this post.

shoober420 commented on 2017-05-24 21:54 (UTC)

The PKGBUILD should overall be updated. I'll take over this package if you want. I'm going to make a 32bit build anyway.

shoober420 commented on 2017-05-24 21:45 (UTC)

"python-lxml" needs added to the makedepends

toropisco commented on 2015-05-31 13:59 (UTC)

Ahhh.... NO! Python is needed *only* if you are using Jam to build freetype or compiling the python extensions, which FYI are a different package. I am definitely not using Jam to compile freetype. IT is incredibly rude to post a comment and then file an out-of-date notification at the same time. Do you want to maintain this package? You are welcome to it, just ask nicely and you can have it.

Polarina commented on 2015-05-31 08:56 (UTC)

There is a missing build dependency: python2

yuyichao commented on 2013-04-24 01:54 (UTC)

I see no advantage using makepkg to download either

Scimmia commented on 2013-04-24 01:44 (UTC)

Which makes no sense whatsoever in an AUR PKGBUILD.

yuyichao commented on 2013-04-23 21:26 (UTC)

To test different branches.

Scimmia commented on 2013-04-23 21:01 (UTC)

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

yuyichao commented on 2013-04-23 11:53 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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. [1]:

yuyichao commented on 2013-04-12 20:54 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

Earnest commented on 2013-04-12 14:24 (UTC)

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 (UTC)

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 (UTC)

pacman 4.1 updated PKGBUILD: