On Mon, 10 Apr 2006 08:18:51 +0200 Kai Blin kai.blin@gmail.com wrote:
Also added fontforge to the build requirements list, with a note to Gentoo users to update their version of fontforge, as the version currently used in Gentoo doesn't work.
Too late: today's Gentoo Portage has fontforge-20060406 (although as a ~x86 unstable package).
-- Ph.
* Phil Krylov phil@newstar.rinet.ru [10/04/06, 11:52:01]:
On Mon, 10 Apr 2006 08:18:51 +0200 Kai Blin kai.blin@gmail.com wrote:
Also added fontforge to the build requirements list, with a note to Gentoo users to update their version of fontforge, as the version currently used in Gentoo doesn't work.
Too late: today's Gentoo Portage has fontforge-20060406 (although as a ~x86 unstable package).
That's what my patch mentions.
+ In order to create your fonts, you will need a recent version of fontforge. + fontforge 20050803 works. NOTE TO GENTOO USERS: fontforge 20050624 does not + work. Use fontforge 20060406 from the ~ARCH repository.
Cheers, Kai
On Mon, 10 Apr 2006 10:05:33 +0200 Kai Blin blin@gmx.net wrote:
- Phil Krylov phil@newstar.rinet.ru [10/04/06, 11:52:01]:
On Mon, 10 Apr 2006 08:18:51 +0200 Kai Blin kai.blin@gmail.com wrote:
Also added fontforge to the build requirements list, with a note to Gentoo users to update their version of fontforge, as the version currently used in Gentoo doesn't work.
Too late: today's Gentoo Portage has fontforge-20060406 (although as a ~x86 unstable package).
That's what my patch mentions.
- In order to create your fonts, you will need a recent version of
fontforge.
- fontforge 20050803 works. NOTE TO GENTOO USERS: fontforge 20050624
does not
- work. Use fontforge 20060406 from the ~ARCH repository.
OK sorry, didn't read the patch...
-- Ph.
Phil Krylov wrote:
On Mon, 10 Apr 2006 10:05:33 +0200 Kai Blin blin@gmx.net wrote:
- Phil Krylov phil@newstar.rinet.ru [10/04/06, 11:52:01]:
On Mon, 10 Apr 2006 08:18:51 +0200 Kai Blin kai.blin@gmail.com wrote:
Also added fontforge to the build requirements list, with a note to Gentoo users to update their version of fontforge, as the version currently used in Gentoo doesn't work.
Too late: today's Gentoo Portage has fontforge-20060406 (although as a ~x86 unstable package).
That's what my patch mentions.
- In order to create your fonts, you will need a recent version of
fontforge.
- fontforge 20050803 works. NOTE TO GENTOO USERS: fontforge 20050624
does not
- work. Use fontforge 20060406 from the ~ARCH repository.
OK sorry, didn't read the patch...
-- Ph.
Add these lines for those people that ask us how to use ~ARCH fontforge instead of RTFMing:
To enable ~ARCH fontforge without setting your whole system ~ARCH, do this (as root):
echo "=media-gfx/fontforge-20060406" >> /etc/portage/package.keywords
On Mon, 10 Apr 2006 04:43:59 -0400 Segin segin2005@gmail.com wrote:
Add these lines for those people that ask us how to use ~ARCH fontforge instead of RTFMing:
To enable ~ARCH fontforge without setting your whole system ~ARCH, do this (as root):
echo "=media-gfx/fontforge-20060406" >> /etc/portage/package.keywords
Is this really preferable to the following?
echo "media-gfx/fontforge ~x86" >> /etc/portage/package.keywords
-- Ph.
On 4/10/06, Phil Krylov phil@newstar.rinet.ru wrote:
On Mon, 10 Apr 2006 04:43:59 -0400 Segin segin2005@gmail.com wrote:
Add these lines for those people that ask us how to use ~ARCH fontforge instead of RTFMing:
To enable ~ARCH fontforge without setting your whole system ~ARCH, do this (as root):
echo "=media-gfx/fontforge-20060406" >> /etc/portage/package.keywords
Is this really preferable to the following?
echo "media-gfx/fontforge ~x86" >> /etc/portage/package.keywords
-- Ph.
Wine only needs version 20060406, so why set it to always pull them from ~ARCH? Someone who wanted to do that would likely be in ~ARCH anyways.
Unless there's a reason to use other ~ARCH versions than 20060406, there's no reason for someone not in ~ARCH to get them (until they're moved out of ~).
--Murph
echo "=media-gfx/fontforge-20060406" >> /etc/portage/package.keywords
echo "media-gfx/fontforge ~x86" >> /etc/portage/package.keywords
Latter version is definitely preferable, as otherwise FontForge will never again be upgraded (right?).
Molle Bestefich wrote:
echo "=media-gfx/fontforge-20060406" >> /etc/portage/package.keywords
echo "media-gfx/fontforge ~x86" >> /etc/portage/package.keywords
Latter version is definitely preferable, as otherwise FontForge will never again be upgraded (right?).
Actually the former is incorrect b/c a keyword isn't specified for the package. You'd need:
echo "=media-gfx/fontforge-20060406 ~x86" >> /etc/portage/package.keywords
(and ~x86 should be ~amd64 for those running 64-bit)
That would have the effect of only allowing that particular _unstable_ version of fontforge to be installed. Once a newer version was marked stable, that version would be superseded. However, the latter one will continually install the most recent unstable version of fontforge. To me, the former seems better if I'm trying to keep an overall stable system.
Ryan
Molle Bestefich wrote:
echo "=media-gfx/fontforge-20060406" >> /etc/portage/package.keywords
echo "media-gfx/fontforge ~x86" >> /etc/portage/package.keywords
Latter version is definitely preferable, as otherwise FontForge will never again be upgraded (right?).
I believe that former version will unmask only given version while latter version will unmask all unstable versions of fontforge, forcing users to update every time new version is available. So, using former version, x86 keyworded systems will be updated to 20060406 version, and will stay on it until more recent version will be marked as stable.
-
Andrey Turkin -
Kai Blin -
Matt Finnicum -
Molle Bestefich -
Phil Krylov -
Ryan May -
Segin