Re: [Mageia-dev] Are we on time?
On Wed, Jun 01, 2011 at 01:48:53AM +0200, Michael Scherer wrote: Le mardi 31 mai 2011 à 18:41 +0200, Anne nicolas a écrit : Guess what... yes :) ( sorry to contradict you ) Last minute check showed 2 problems : - the dual iso is too big ( ~56 mo too big, maybe because of samba ), so it doesn't fit on a regular cd. Pterjan found some fix in bcd to reduce that problem. - the dual is not hybrid ( the first sector are empty ), as seen by hexedit ( so it doesn't boot on usb ). It seems to miss a call to isohybrid -fatfirst We removed the dual for now from main mirror, and we will likely have to remaster it for the first issue. We didn't decide yet if we ship the iso as is with a newer version later or not ( as the iso work, except for those 2 issues, and the 2nd one is easy to fix ). I think issue #1 would make the ISO worthless for most of the intended audience. Also, as I think the CD image will be preferred by people over the DVD image who are on a limited connections, I think we should not release an ISO file that's too big; It would not be a very positive first impression for them with Mageia. My two cents worth. Sleep tight all and thanks for all the hard work :-) Remmy signature.asc Description: Digital signature
Re: [Mageia-dev] Are we on time?
Le mardi 31 mai 2011 à 18:41 +0200, Anne nicolas a écrit : > Guess what... yes :) ( sorry to contradict you ) Last minute check showed 2 problems : - the dual iso is too big ( ~56 mo too big, maybe because of samba ), so it doesn't fit on a regular cd. Pterjan found some fix in bcd to reduce that problem. - the dual is not hybrid ( the first sector are empty ), as seen by hexedit ( so it doesn't boot on usb ). It seems to miss a call to isohybrid -fatfirst We removed the dual for now from main mirror, and we will likely have to remaster it for the first issue. We didn't decide yet if we ship the iso as is with a newer version later or not ( as the iso work, except for those 2 issues, and the 2nd one is easy to fix ). -- Michael Scherer
[Mageia-dev] Are we on time?
Guess what... yes :) So tests for final isos are now done and all isos ready for upload. Stable repository will be uploaded now so that it can be spread on mirrors. Everything will be ready on time for tomorrow big day. Many thanks to everybody for hard work and especially testers of this final release. Cauldron should reopen by the end of this week, it will give some time to setup everything for updates on Mageia1. Cheers -- Anne http://www.mageia.org
Re: [Mageia-dev] Tainted build
On 31 May 2011 16:38, Romain d'Alverny wrote: > On Tue, May 31, 2011 at 16:31, andre999 wrote: >> Michael Scherer a écrit : >>> Supixel rendering, there is a patent on it : >>> http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html >>> >> The reference is from September 2006, almost 5 years old. There is no >> indication of expiry dates, and rather limited details on the patent claims >> involved, apparently now held by Microsoft. (The further link to Microsoft >> is no longer valid.) >> It would seem advisable to have more info before making a decision. > > And you're welcome to search for it and document this situation. Such as with: > > * http://www.freetype.org/patents.html > * http://en.wikipedia.org/wiki/ClearType#Patents > * http://en.wikipedia.org/wiki/Subpixel_rendering#Patents > > Said patents are due to expire in 2018/19 according to these sources. > > Romain > One more source, the all very-extensive http://david.freetype.org/cleartype-patents.html written by the freetype upstream lead dev. -- Ahmad Samir
Re: [Mageia-dev] Tainted build
On Tue, May 31, 2011 at 16:31, andre999 wrote: > Michael Scherer a écrit : >> Supixel rendering, there is a patent on it : >> http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html >> > The reference is from September 2006, almost 5 years old. There is no > indication of expiry dates, and rather limited details on the patent claims > involved, apparently now held by Microsoft. (The further link to Microsoft > is no longer valid.) > It would seem advisable to have more info before making a decision. And you're welcome to search for it and document this situation. Such as with: * http://www.freetype.org/patents.html * http://en.wikipedia.org/wiki/ClearType#Patents * http://en.wikipedia.org/wiki/Subpixel_rendering#Patents Said patents are due to expire in 2018/19 according to these sources. Romain
Re: [Mageia-dev] Tainted build
Michael Scherer a écrit : Le mardi 31 mai 2011 à 05:33 +0200, Tux99 a écrit : I thought the core build of freetype2 already has the bytecode interpreter enabled (since the patent expired). Why is there still a need for a tainted version? Supixel rendering, there is a patent on it : http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html The reference is from September 2006, almost 5 years old. There is no indication of expiry dates, and rather limited details on the patent claims involved, apparently now held by Microsoft. (The further link to Microsoft is no longer valid.) It would seem advisable to have more info before making a decision. Microsoft is notarious for bogus (non-enforceable) patent claims. (Like their vague patent on the essential elements of a spreadsheet, issued long after the development of the spreadsheet.) -- André
Re: [Mageia-dev] Tainted build
Le mardi 31 mai 2011 à 05:33 +0200, Tux99 a écrit : > > I thought the core build of freetype2 already has the bytecode interpreter > enabled (since the patent expired). > Why is there still a need for a tainted version? Supixel rendering, there is a patent on it : http://lists.gnu.org/archive/html/freetype/2006-09/msg00064.html -- Michael Scherer
