From mint-bounce@lists.fishpool.fi Thu Jun 3 16:22:04 2010 Date: Thu, 3 Jun 2010 16:19:46 -0400 (EDT) From: Keith Scroggins To: mint@lists.fishpool.fi Subject: Re: [MiNT] Porting newer version of libfreetype In-Reply-To: <3b62d18b86b10159c59128a5f6eda5fa-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYJXlhoA1VcMl5dRkAHVlhfQls=-webmailer2@server07.webmailer.hosteurope.de> Message-ID: References: <3b62d18b86b10159c59128a5f6eda5fa-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYJXlhoA1VcMl5dRkAHVlhfQls=-webmailer2@server07.webmailer.hosteurope.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: kws@radix.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hello Ole, If you want to work on it and update SpareMiNT, I say go right ahead, that is basically the only way software will be updated. As far as the patches, just compare them with the source to see if they are even relevent. Some of Frank's patches were for specific issues he uncovered, while others were patches already available to fix issues discovered after release. As far as the patches, you could submit your patches to the current dev's to see if they are accepted, so only the current version need patching, and the next release will remove that requirement. Basically, I think any package in SpareMiNT is fair game for updates, and more packages are welcomed! Keith On Thu, 3 Jun 2010, Ole Loots wrote: > Hello, > > it would be good to have a newer version of libfreetype for sparemint, > because the netsurf browser can use that as an font backend if you > configure it in the make files. The internal rendering seems to be buggy > with Atari (and Amiga also, they suggest using freetype). > > Because the Netsurf freetype usage depends on some newer structs, I would > like to port a newer version ( > 2.3.x ) . > > Frank Naumann ported the 2.0 package. > > He included some patches in the rpm. Is there an specific way how to > transport these patches into the newer official releases? Or should I look > into the 2.3.x sources, find the critical code lines and create new > patches? Of course, I'm not talking about applying the patches to the > current release... I just don't like the thought that we need to create a > new patch, everytime we compile a new version.... > > Maybe there is an "official" way how to handle it... it seems a bit sad > that fixes for sparemint (mostly) ain't go into the "official" packages :) > > > >