Reorganize the templates directory for possible future changes.
Now every template uses its own directory. Patches, prepost* files and other related stuff are stored there. --HG-- extra : convert_revision : bbc529ef161d9a59fe13a1d54ac058f77ea05845
This commit is contained in:
parent
6c252d43d4
commit
fa2748d9b2
291 changed files with 25 additions and 24 deletions
22
templates/libXft/template
Normal file
22
templates/libXft/template
Normal file
|
@ -0,0 +1,22 @@
|
|||
# Template build file for 'libXft'.
|
||||
pkgname=libXft
|
||||
version=2.1.13
|
||||
distfiles="
|
||||
http://xorg.freedesktop.org/releases/individual/lib/$pkgname-$version.tar.bz2"
|
||||
build_style=gnu_configure
|
||||
make_cmd="$XBPS_MASTERDIR/bin/gmake"
|
||||
pkgconfig_override="xft.pc"
|
||||
short_desc="Library for configuring and customizing font access"
|
||||
maintainer="Juan RP <xtraeme@gmail.com>"
|
||||
checksum=f9cbfd6710a9999a12f49e2bb23b8061eee01e9e
|
||||
long_desc="
|
||||
Xft (2.0) provides a client-side font API for X applications. It uses
|
||||
Fontconfig to select fonts and the X protocol for rendering them. When
|
||||
available, Xft uses the Render extension to accelerate text drawing.
|
||||
When Render is not available, Xft uses the core protocol to draw
|
||||
client-side glyphs. This provides completely compatible support of
|
||||
client-side fonts for all X servers.
|
||||
|
||||
Xft (2.0) hides most of the underlying system details so that developers
|
||||
can confidently use its API to access client-side fonts in any X
|
||||
environment."
|
Loading…
Add table
Add a link
Reference in a new issue