Re: [Mageia-dev] Freeze push request: flash-player-plugin
2011/5/13 Anssi Hannula : > This is an upgrade to flash player 10.3, which we always need the latest > version of (security etc). done > > -- > Anssi Hannula > -- Anne http://www.mageia.org
[Mageia-dev] Freeze push request: flash-player-plugin
This is an upgrade to flash player 10.3, which we always need the latest version of (security etc). -- Anssi Hannula
[Mageia-dev] Freeze push request: wine
Please submit wine, this updates it to 1.3.20, with the usual plethora of bug fixes that comes with a new version of wine. -- Ahmad Samir
Re: [Mageia-dev] Problem with update notification
On 13 May 2011 20:09, Thibaut FRANCOIS wrote: > > > 2011/5/13 Ahmad Samir >> >> On 13 May 2011 19:47, Thibaut FRANCOIS wrote: >> > Hello, >> > >> > I updated my desktop computer from mandriva 2010.2 to mageia cauldron. >> > Everything works fine, except one thing : >> > when the "update notification" is red on my taskbar, I click on, but >> > instead >> > of launching mageiaupdate, there is only a new medias scan (the >> > indicator is >> > orange) and finally the indicator became red again. >> > >> > Am I alone with this problem ? >> > >> > Regards, >> > Thibaut >> > PS : I'm using KDE >> > >> >> You probably still have mdkonline; you need mgaonline which has only >> been available less than an hour ago, and it should automatically >> obsolete mdkonline when you update your system. >> >> -- >> Ahmad Samir > > Right, mdkonline is installed on my systme. I'm waiting the update with > mgaonline and I will verify the notification after. > Thanks > > Thibaut > (Please always post plain text emails when posting to public mailing lists, this is the preferred format). -- Ahmad Samir
Re: [Mageia-dev] Problem with update notification
2011/5/13 Ahmad Samir > On 13 May 2011 19:47, Thibaut FRANCOIS wrote: > > Hello, > > > > I updated my desktop computer from mandriva 2010.2 to mageia cauldron. > > Everything works fine, except one thing : > > when the "update notification" is red on my taskbar, I click on, but > instead > > of launching mageiaupdate, there is only a new medias scan (the indicator > is > > orange) and finally the indicator became red again. > > > > Am I alone with this problem ? > > > > Regards, > > Thibaut > > PS : I'm using KDE > > > > You probably still have mdkonline; you need mgaonline which has only > been available less than an hour ago, and it should automatically > obsolete mdkonline when you update your system. > > -- > Ahmad Samir > Right, mdkonline is installed on my systme. I'm waiting the update with mgaonline and I will verify the notification after. Thanks Thibaut
Re: [Mageia-dev] Problem with update notification
On 13 May 2011 19:47, Thibaut FRANCOIS wrote: > Hello, > > I updated my desktop computer from mandriva 2010.2 to mageia cauldron. > Everything works fine, except one thing : > when the "update notification" is red on my taskbar, I click on, but instead > of launching mageiaupdate, there is only a new medias scan (the indicator is > orange) and finally the indicator became red again. > > Am I alone with this problem ? > > Regards, > Thibaut > PS : I'm using KDE > You probably still have mdkonline; you need mgaonline which has only been available less than an hour ago, and it should automatically obsolete mdkonline when you update your system. -- Ahmad Samir
[Mageia-dev] Problem with update notification
Hello, I updated my desktop computer from mandriva 2010.2 to mageia cauldron. Everything works fine, except one thing : when the "update notification" is red on my taskbar, I click on, but instead of launching mageiaupdate, there is only a new medias scan (the indicator is orange) and finally the indicator became red again. Am I alone with this problem ? Regards, Thibaut PS : I'm using KDE
Re: [Mageia-dev] Freeze push request: fglrx 8.850
On Fri, May 13, 2011 at 03:40:51AM +0300, Anssi Hannula wrote: > I think the new version 8.85 should be pushed, changes include > - fixes intel/fglrx switching on PowerXpress > - fixes some cases of suspend not working > > Especially the first change is something that would be nice, since the > ATI version we have now claims to support it as well but fails to work > (it tries to mv libraries around manually; not sure how cleanly it fails > with our alternatives), confusing users. done -- Michael Scherer
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
On Friday, 13 May 2011 17:28:24 Zé wrote: > 2011/5/13 Buchan Milne : > > On Friday, 13 May 2011 11:12:41 Zé wrote: > >> 2011/5/13 Zé : > >> > 2011/5/13 Dimitrios Glentadakis : > >> >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε: > >> >>> 2011/5/12 Dick Gevers : > >> >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote > >> >>> > about > >> >>> > >> >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\* > >> >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER \*/|' > >> >>> include/freetype/config/ftoption.h > >> >>> > >> >>> > >> >>> dont forget to also increase Release to avoid conflicts with > >> >>> existant freetype2, and then build the package. > >> >> > >> >> Why do all these things when you can simply add an entry in the > >> >> font.conf file ? > >> > > >> > Thats a fact, but hat should happen is that freetype2 should have > >> > bytecode interpreter disabled by default, since so far users prefer > >> > it. > >> > >> Seams Fedora choosed to finally fix it, it reverted freetype2 with a > >> patch to disable bytecode interpreter. -> > >> https://bugzilla.redhat.com/show_bug.cgi?id=547532 > > > > No, this is not what is covered in this bug report. > > Yes, correct i miss understood what as the bug report about. > > > Firstly, here are the non-problems: > > 1)The bytecode interpreter *can* make fonts look better, *if* they have > > hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the > > MS fonts *do* have hinting. > > > > So, historically, the recommended approach was to use the PLF freetype > > *if* you had imported MS fonts (e.g. from a dual-boot Windows > > installation). > > Well i always avoid using PLF freetype and for what i have read in > ML's all the users that answered to it said that also avoid PLF > freetype. > > So far for hat i have seen, all users prefered like fonts were > rendered wen patents were still valid... Were *all* these users using *hinted* fonts? I think they weren't using hinted fonts at all. > > 2)The Freetype autohinter was implemented later, and improves things for > > unhinted fonts, but hinted fonts still looked better with the bytecode > > interpreter. > > > > > > This is the problem: > > 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or, > > could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts. > > > > The Fedora bug isn't about disabling the bytecode interpreter, but by > > still allowing auto-hinting for unhinted fonts if the bytecode > > interpreter. > > > > *This* is the right fix. Your insistence to *disable* the bytecode > > interpreter (leaving users with *no* options, in case they need hinted > > fonts) is the wrong fix. > > Well this way users cant also set to have autohint, seams theres > always some app failing. ? We need to apply the patch that enables the autohinter for unhinted fonts, even if the bytecode interpreter is enabled, that is available from the bug report for which you provided the link. > Why not having it disabled by default? So, you haven't read what I wrote in (3)? > users will always be able to > set their preferences about using or not autohint, but that way > ensures that all fonts are better rended. No, you ignore the case where some hinted fonts are almost unusable without the bytecode interpreter, and others where they are rendered better. > All this came up after patents end in wich showed users how fonts > appear poor rended, until that point i didnt saw any complains about > fonts, and this is what should be fixed. You contradict yourself ... and you can't make blanket statements of "how fonts appear poor rended", as it depends on the font (and whether it is hinted or not). Regards, Buchan
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
On 13 May 2011 12:09, Buchan Milne wrote: > > No, this is not what is covered in this bug report. > > Firstly, here are the non-problems: > 1)The bytecode interpreter *can* make fonts look better, *if* they have > hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS > fonts *do* have hinting. > > So, historically, the recommended approach was to use the PLF freetype *if* > you had imported MS fonts (e.g. from a dual-boot Windows installation). > > 2)The Freetype autohinter was implemented later, and improves things for > unhinted fonts, but hinted fonts still looked better with the bytecode > interpreter. > > > This is the problem: > 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or, > could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts. > > The Fedora bug isn't about disabling the bytecode interpreter, but by still > allowing auto-hinting for unhinted fonts if the bytecode interpreter. > > *This* is the right fix. Your insistence to *disable* the bytecode interpreter > (leaving users with *no* options, in case they need hinted fonts) is the wrong > fix. > > But, thanks for the pointer to the bug, which points to the patches. Anssi has already added that patch to the Mageia freetype2 package about 2-3 months ago. [...] -- Ahmad Samir
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
2011/5/13 Buchan Milne : > On Friday, 13 May 2011 11:12:41 Zé wrote: >> 2011/5/13 Zé : >> > 2011/5/13 Dimitrios Glentadakis : >> >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε: >> >>> 2011/5/12 Dick Gevers : >> >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about > >> >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\* >> >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER \*/|' >> >>> include/freetype/config/ftoption.h >> >>> >> >>> >> >>> dont forget to also increase Release to avoid conflicts with existant >> >>> freetype2, and then build the package. >> >> >> >> Why do all these things when you can simply add an entry in the >> >> font.conf file ? >> > >> > Thats a fact, but hat should happen is that freetype2 should have >> > bytecode interpreter disabled by default, since so far users prefer >> > it. >> >> Seams Fedora choosed to finally fix it, it reverted freetype2 with a >> patch to disable bytecode interpreter. -> >> https://bugzilla.redhat.com/show_bug.cgi?id=547532 > > No, this is not what is covered in this bug report. Yes, correct i miss understood what as the bug report about. > Firstly, here are the non-problems: > 1)The bytecode interpreter *can* make fonts look better, *if* they have > hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS > fonts *do* have hinting. > > So, historically, the recommended approach was to use the PLF freetype *if* > you had imported MS fonts (e.g. from a dual-boot Windows installation). Well i always avoid using PLF freetype and for what i have read in ML's all the users that answered to it said that also avoid PLF freetype. So far for hat i have seen, all users prefered like fonts were rendered wen patents were still valid... > 2)The Freetype autohinter was implemented later, and improves things for > unhinted fonts, but hinted fonts still looked better with the bytecode > interpreter. > > > This is the problem: > 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or, > could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts. > > The Fedora bug isn't about disabling the bytecode interpreter, but by still > allowing auto-hinting for unhinted fonts if the bytecode interpreter. > > *This* is the right fix. Your insistence to *disable* the bytecode interpreter > (leaving users with *no* options, in case they need hinted fonts) is the wrong > fix. Well this way users cant also set to have autohint, seams theres always some app failing. Why not having it disabled by default? users will always be able to set their preferences about using or not autohint, but that way ensures that all fonts are better rended. All this came up after patents end in wich showed users how fonts appear poor rended, until that point i didnt saw any complains about fonts, and this is what should be fixed. > But, thanks for the pointer to the bug, which points to the patches. > >> Why dont we also do the same thing? >> >> Since theres users complaining about it, why not solve it once for all? > > Regards, > Buchan > -- Zé
Re: [Mageia-dev] Samba update to 3.5.8
On Friday, 13 May 2011 12:28:45 Colin Guthrie wrote: > 'Twas brillig, and Buchan Milne at 13/05/11 11:16 did gyre and gimble: > > I have finally got a bit of time to get busy with Mageia packaging (my > > first VM was on virtio disk on Mandriva 2010.1/kvm, and there seem to be > > some corruption problems, I finally got time to reinstall it yesterday). > > > > Since I have just finished samba/samba4 updates in Cooker, I would like > > to update Cauldron to the same. > > > > Specifically, what we miss between 3.5.5+CVE is: > > > > > > New in 3.5.8: > > o Fix Winbind crash bug when no DC is available (bug #7730). > > o Fix finding users on domain members (bug #7743). > > o Fix memory leaks in Winbind (bug #7879). > > o Fix printing with Windows 7 clients (bug #7567). > > > > New in 3.5.6: > > o Fix smbd panic on invalid NetBIOS session request (bug #7698). > > o Fix smbd crash caused by "%D" in "printer admin" (bug #7541). > > o Fix crash bug with invalid SPNEGO token (bug #7694). > > o Fix Winbind internal error (bug #7636). > > > > Unfortunately, "samba features", if absent, are usually "samba bugs", > > such as printing with Windows 7 clients etc. > > > > If this is viable, I will try and commit updates to the following in svn > > between now and 15h00 UTC: > > > > -tdb 1.2.9 (done) > > -ldb 1.1.0 (import) I could probably submit this now, but it (build)requires tdb-1.2.9. Its other requirement, fixed package names/provides for talloc, has just finished building. > > -samba-3.5.8 > > -samba4alpha15 (alpha11 was imported about 2 days before I finished > > alpha15 in Mandriva) > > > > Please let me know if I should go ahead. tdb should be pushed in the > > meantime in this case. > > While this is very late in the cycle, the changes to samba look like > bugfixes to me and the samba4alpha package is likely one we can push > through the freeze anyway due to it's nature. > > So IMO the only question is the tdb and ldb. Are these just bug fixes > too? (as ldb is an import it's less of an issue - is it just needed for > samba4?) Both samba3 and samba4 require newer versions of tdb, and ldb, I've switched to using standalone versions of all the common libraries (talloc,tdb,tevent,ldb) now that they actually seem to be released before versions of samba3/samba4 that need them. (By default, without the libraries, both versions of samba would build static- only copies, or you can choose to build shared libraries, but it ends up being more convoluted having them in one or the other of samba3 or samba4). Regards, Buchan
Re: [Mageia-dev] Samba update to 3.5.8
'Twas brillig, and Buchan Milne at 13/05/11 11:16 did gyre and gimble: > I have finally got a bit of time to get busy with Mageia packaging (my first > VM was on virtio disk on Mandriva 2010.1/kvm, and there seem to be some > corruption problems, I finally got time to reinstall it yesterday). > > Since I have just finished samba/samba4 updates in Cooker, I would like to > update Cauldron to the same. > > Specifically, what we miss between 3.5.5+CVE is: > > > New in 3.5.8: > o Fix Winbind crash bug when no DC is available (bug #7730). > o Fix finding users on domain members (bug #7743). > o Fix memory leaks in Winbind (bug #7879). > o Fix printing with Windows 7 clients (bug #7567). > > New in 3.5.6: > o Fix smbd panic on invalid NetBIOS session request (bug #7698). > o Fix smbd crash caused by "%D" in "printer admin" (bug #7541). > o Fix crash bug with invalid SPNEGO token (bug #7694). > o Fix Winbind internal error (bug #7636). > > Unfortunately, "samba features", if absent, are usually "samba bugs", such as > printing with Windows 7 clients etc. > > If this is viable, I will try and commit updates to the following in svn > between now and 15h00 UTC: > > -tdb 1.2.9 (done) > -ldb 1.1.0 (import) > -samba-3.5.8 > -samba4alpha15 (alpha11 was imported about 2 days before I finished alpha15 > in > Mandriva) > > Please let me know if I should go ahead. tdb should be pushed in the meantime > in this case. While this is very late in the cycle, the changes to samba look like bugfixes to me and the samba4alpha package is likely one we can push through the freeze anyway due to it's nature. So IMO the only question is the tdb and ldb. Are these just bug fixes too? (as ldb is an import it's less of an issue - is it just needed for samba4?) Col -- Colin Guthrie mageia(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
[Mageia-dev] Samba update to 3.5.8
I have finally got a bit of time to get busy with Mageia packaging (my first VM was on virtio disk on Mandriva 2010.1/kvm, and there seem to be some corruption problems, I finally got time to reinstall it yesterday). Since I have just finished samba/samba4 updates in Cooker, I would like to update Cauldron to the same. Specifically, what we miss between 3.5.5+CVE is: New in 3.5.8: o Fix Winbind crash bug when no DC is available (bug #7730). o Fix finding users on domain members (bug #7743). o Fix memory leaks in Winbind (bug #7879). o Fix printing with Windows 7 clients (bug #7567). New in 3.5.6: o Fix smbd panic on invalid NetBIOS session request (bug #7698). o Fix smbd crash caused by "%D" in "printer admin" (bug #7541). o Fix crash bug with invalid SPNEGO token (bug #7694). o Fix Winbind internal error (bug #7636). Unfortunately, "samba features", if absent, are usually "samba bugs", such as printing with Windows 7 clients etc. If this is viable, I will try and commit updates to the following in svn between now and 15h00 UTC: -tdb 1.2.9 (done) -ldb 1.1.0 (import) -samba-3.5.8 -samba4alpha15 (alpha11 was imported about 2 days before I finished alpha15 in Mandriva) Please let me know if I should go ahead. tdb should be pushed in the meantime in this case. Regards, Buchan
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
On Friday, 13 May 2011 11:12:41 Zé wrote: > 2011/5/13 Zé : > > 2011/5/13 Dimitrios Glentadakis : > >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε: > >>> 2011/5/12 Dick Gevers : > >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about > >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\* > >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER \*/|' > >>> include/freetype/config/ftoption.h > >>> > >>> > >>> dont forget to also increase Release to avoid conflicts with existant > >>> freetype2, and then build the package. > >> > >> Why do all these things when you can simply add an entry in the > >> font.conf file ? > > > > Thats a fact, but hat should happen is that freetype2 should have > > bytecode interpreter disabled by default, since so far users prefer > > it. > > Seams Fedora choosed to finally fix it, it reverted freetype2 with a > patch to disable bytecode interpreter. -> > https://bugzilla.redhat.com/show_bug.cgi?id=547532 No, this is not what is covered in this bug report. Firstly, here are the non-problems: 1)The bytecode interpreter *can* make fonts look better, *if* they have hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS fonts *do* have hinting. So, historically, the recommended approach was to use the PLF freetype *if* you had imported MS fonts (e.g. from a dual-boot Windows installation). 2)The Freetype autohinter was implemented later, and improves things for unhinted fonts, but hinted fonts still looked better with the bytecode interpreter. This is the problem: 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or, could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts. The Fedora bug isn't about disabling the bytecode interpreter, but by still allowing auto-hinting for unhinted fonts if the bytecode interpreter. *This* is the right fix. Your insistence to *disable* the bytecode interpreter (leaving users with *no* options, in case they need hinted fonts) is the wrong fix. But, thanks for the pointer to the bug, which points to the patches. > Why dont we also do the same thing? > > Since theres users complaining about it, why not solve it once for all? Regards, Buchan
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
2011/5/13 Zé : > 2011/5/13 Zé : >> Thats a fact, but hat should happen is that freetype2 should have >> bytecode interpreter disabled by default, since so far users prefer >> it. > Seams Fedora choosed to finally fix it, it reverted freetype2 with a > patch to disable bytecode interpreter. -> > https://bugzilla.redhat.com/show_bug.cgi?id=547532 > Why dont we also do the same thing? > Since theres users complaining about it, why not solve it once for all? > -- > Zé > Hello, Is this thread asking to _disable_ bytecode interpreter? Please don't do that. Bacause pdf which embedded with Windows Chinese fonts will look like this if you disabled bytecode interpreter: http://hyperrate.com/thread.php?tid=680 For years we have to either rebuild freetype, or use plf package. Since there's no patent problems now, I beg you, seriously, please do not disable bytecode interpreter in freetype. Sincerely, You-Cheng Hsieh
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
2011/5/13 Zé : > 2011/5/13 Dimitrios Glentadakis : >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε: >>> 2011/5/12 Dick Gevers : >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re: >>> > [Mageia-dev] why not disable bytecode interpreter in freetype2 ?: >>> > >>> >>When someone like me, has this problem of fonts, he cannot even use his >>> >>system, he has a real problem. It costed me many uninstalls and installs >>> >>and many hours of investigation. >>> >> >>> >>For that i asked a user friendly solution, is very important for them who >>> >>are affected. >>> >> >>> >>Personnaly, after all, i am able now to set my pc to fit my needs but i >>> >>continue to search a solution for other users who will be front of this >>> >>problem in the future >>> > >>> > I can only make one suggestion - which works for me: keep the version one >>> > is happy with and put the packages in the urpmi skip.list and you won't >>> > get >>> > hurt by an upgrade. >>> > >>> > Cheers, >>> > =Dick Gevers= >>> > >>> >>> You always rebuild the freetype2 package, to do soedit the .spec file, >>> in the section %prep add this: >>> >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\* >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER \*/|' >>> include/freetype/config/ftoption.h >>> >>> >>> dont forget to also increase Release to avoid conflicts with existant >>> freetype2, and then build the package. >>> >>> >> >> >> Why do all these things when you can simply add an entry in the font.conf >> file ? > > Thats a fact, but hat should happen is that freetype2 should have > bytecode interpreter disabled by default, since so far users prefer > it. Seams Fedora choosed to finally fix it, it reverted freetype2 with a patch to disable bytecode interpreter. -> https://bugzilla.redhat.com/show_bug.cgi?id=547532 Why dont we also do the same thing? Since theres users complaining about it, why not solve it once for all? -- Zé
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
2011/5/13 Dimitrios Glentadakis : > Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε: >> 2011/5/12 Dick Gevers : >> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re: >> > [Mageia-dev] why not disable bytecode interpreter in freetype2 ?: >> > >> >>When someone like me, has this problem of fonts, he cannot even use his >> >>system, he has a real problem. It costed me many uninstalls and installs >> >>and many hours of investigation. >> >> >> >>For that i asked a user friendly solution, is very important for them who >> >>are affected. >> >> >> >>Personnaly, after all, i am able now to set my pc to fit my needs but i >> >>continue to search a solution for other users who will be front of this >> >>problem in the future >> > >> > I can only make one suggestion - which works for me: keep the version one >> > is happy with and put the packages in the urpmi skip.list and you won't get >> > hurt by an upgrade. >> > >> > Cheers, >> > =Dick Gevers= >> > >> >> You always rebuild the freetype2 package, to do soedit the .spec file, >> in the section %prep add this: >> >> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\* >> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER \*/|' >> include/freetype/config/ftoption.h >> >> >> dont forget to also increase Release to avoid conflicts with existant >> freetype2, and then build the package. >> >> > > > Why do all these things when you can simply add an entry in the font.conf > file ? Forgot to refer that even when you set it in .fonts.conf you will still have it in some situations, check http://www.webmasterkb.com/Uwe/Forum.aspx/opera-linux/2140/disabling-bytecode-interpreter-font-rendering > -- > Dimitrios Glentadakis > -- Zé
Re: [Mageia-dev] why not disable bytecode interpreter in freetype2 ?
2011/5/13 Dimitrios Glentadakis : > Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε: >> 2011/5/12 Dick Gevers : >> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re: >> > [Mageia-dev] why not disable bytecode interpreter in freetype2 ?: >> > >> >>When someone like me, has this problem of fonts, he cannot even use his >> >>system, he has a real problem. It costed me many uninstalls and installs >> >>and many hours of investigation. >> >> >> >>For that i asked a user friendly solution, is very important for them who >> >>are affected. >> >> >> >>Personnaly, after all, i am able now to set my pc to fit my needs but i >> >>continue to search a solution for other users who will be front of this >> >>problem in the future >> > >> > I can only make one suggestion - which works for me: keep the version one >> > is happy with and put the packages in the urpmi skip.list and you won't get >> > hurt by an upgrade. >> > >> > Cheers, >> > =Dick Gevers= >> > >> >> You always rebuild the freetype2 package, to do soedit the .spec file, >> in the section %prep add this: >> >> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\* >> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER \*/|' >> include/freetype/config/ftoption.h >> >> >> dont forget to also increase Release to avoid conflicts with existant >> freetype2, and then build the package. >> >> > > > Why do all these things when you can simply add an entry in the font.conf > file ? Thats a fact, but hat should happen is that freetype2 should have bytecode interpreter disabled by default, since so far users prefer it. > -- > Dimitrios Glentadakis > -- Zé
