You are not logged in.
Pages: 1
Fontmatrix is the first really decent font manager for Linux -- should be on every desktop, at least when it's finished. It is still in relatively early development, but it is already a very good tool for managing fonts, and I have the developer's word for it, that when it's done, it will have everything one can possibly desire
Bruce Byfeld just wrote a raving review of it ("Finally, the long wait for a GNU/Linux font manager is ending.")
http://www.linux.com/feature/122156.
Anyway, I made a package for the svn version -- things happen fast these days, so one might as well go with that, and it runs without a glitch here. Please let me know if something in the pkgbuild should be changed. the -DCMAKE part I copied from some other svn package -- I don't know svn, but it gets the files in the right place..
# Contributor: Eyolf Østrem <eyolf@oestrem.com>
pkgname=fontmatrix-svn
pkgver=0.2svn
pkgrel=1
pkgdesc="A font manager for the Linux desktop"
arch=('i686')
url="http://www.fontmatrix.net/"
license=('GPL')
depends=('qt>=4.3' 'freetype2')
provides=('fontmatrix')
conflicts=('fontmatrix')
makedepends=('svn')
source=()
md5sums=()
build() {
cd $startdir/src
svn co http://svn.gna.org/svn/undertype/trunk/tools/typotek
cd typotek
cmake . -DCMAKE_INSTALL_PREFIX:PATH=/usr
make || return 1
make DESTDIR=$startdir/pkg install || return 1
}
Offline
please follow the Arch Packaging Standards: http://wiki.archlinux.org/index.php/Arc … _Standards
especially pay attention to the part on svn/cvs packages.
Offline
These are PKGBUILDs for fontmatrix I wrote.
for 0.2svn:
pkgname=fontmatrix
pkgver=0.2svn
pkgrel=1
pkgdesc="A font manager for Linux users"
arch=('i686')
url="http://www.fontmatrix.net/"
license=('GPL')
depends=('freetype2' 'qt4')
conflicts=('fontmatrix-svn')
source=(http://www.fontmatrix.net/archives/$pkgname-$pkgver.tar.gz)
md5sums=('a02b1d632826c3824cfceb923dd4bec0')
build() {
cd $startdir/src/$pkgname-$pkgver
qmake -o Makefile typotek.pro || return 1
make || return 1
mkdir -p $startdir/pkg/usr/bin
mkdir -p $startdir/pkg/usr/share/applications
mkdir -p $startdir/pkg/usr/share/pixmaps
install -m755 bin/fontmatrix $startdir/pkg/usr/bin/
install -m644 fontmatrix.desktop $startdir/pkg/usr/share/applications/
install -m644 fontmatrix.png $startdir/pkg/usr/share/pixmaps/
}
for svn version:
pkgname=fontmatrix-svn
pkgver=202
pkgrel=1
pkgdesc="A font manager for Linux users"
arch=('i686')
url="http://www.fontmatrix.net/"
license=('GPL')
depends=('freetype2' 'qt4')
makedepends=('cmake' 'subversion')
provides=('fontmatrix')
conflicts=('fontmatrix')
source=()
md5sums=()
_svntrunk="http://svn.gna.org/svn/undertype/trunk/tools/typotek"
_svnmod="fontmatrix"
build() {
cd $startdir/src
if [ -d $_svnmod/.svn ]; then
(cd $_svnmod && svn up -r $pkgver)
else
svn co $_svntrunk --config-dir ./ -r $pkgver $_svnmod
fi
msg "SVN checkout done or server timeout"
msg "Starting make..."
cp -r $_svnmod $_svnmod-build
cd $_svnmod-build
cmake . -DCMAKE_INSTALL_PREFIX:PATH=/usr || return 1
make || return 1
make DESTDIR=$startdir/pkg install || return 1
}
Last edited by noonov (2007-12-07 13:32:42)
Offline
please follow the Arch Packaging Standards: http://wiki.archlinux.org/index.php/Arc … _Standards
especially pay attention to the part on svn/cvs packages.
For future reference: could you explain what's wrong with the PKGBUILD? I missed out the cmake dependency, that's true, and some of the svn-related code in the build block (at least compared to the other PKGBUILD that was presented) which is presented as an option under the tips section, and not as a requirement, but other than that?
And, yes, I did look at the Packaging Standards page first...
Last edited by eyolf (2007-12-07 15:45:08)
Offline
Hi!
These are PKGBUILDs for fontmatrix I wrote.
for svn version:
...
Thank you for build. It works on x86_64
Pls, submit it to AUR
Sincerely,
Gour
Offline
pressh wrote:please follow the Arch Packaging Standards: http://wiki.archlinux.org/index.php/Arc … _Standards
especially pay attention to the part on svn/cvs packages.
For future reference: could you explain what's wrong with the PKGBUILD? I missed out the cmake dependency, that's true, and some of the svn-related code in the build block (at least compared to the other PKGBUILD that was presented) which is presented as an option under the tips section, and not as a requirement, but other than that?
And, yes, I did look at the Packaging Standards page first...
exactly what you say, you need the _svnmod, _svntrunk, and other stuff from the svn proto PKGBUILD in the wiki.
Other than that there wasn't much wrong with the PKGBUILD.
Offline
Then the wiki page should perhaps be revised: if these are REQUIRED lines, they should not be under "Some tips" and use formulations like "it is usually possible to build in a separate build dir" and "you can use".
Offline
yup, I actually think the first PKGBUILD posted to this thread are the clearest one so I can't see why it should be made REQUIRED.
KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein
Offline
So what does a Font Manager do?
Offline
So what does a Font Manager do?
It is a tool for designers that lets you install or uninstall fonts very easily (by family, by search, etc)
When you have thousands of fonts, having them all enabled is inviable. (Imagine the size of the combobox in your writing application).
Offline
Pages: 1