easyh10-devel Mailing List for EasyH10
Status: Beta
Brought to you by:
nyaochi
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(10) |
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: nyaochi <ny...@ny...> - 2006-06-15 00:24:51
|
Hi all, EasyH10 1.4 was released although It shouldn't have taken so long to release this. Apologies for those who has been working on and waiting for this release. Cheers, Nyaochi |
From: nyaochi <ny...@ny...> - 2006-05-12 17:12:16
|
Hi all, As you might know, there has been a trouble with the CVS server at sourceforge.net lately. Please find the information sent from the sourceforge.net if you are using the developer CVS. The name of the CVS server is going to be changed. Please also be careful for the consistency of the source code as they might have lost some last-minutes commits to the CVS. Best wishes, Nyaochi -------- Original Message -------- Subject: SUBJECT: SourceForge.net: CVS service offering changes Date: Thu, 11 May 2006 18:20:38 -0700 (PDT) From: SourceForge.net Team <no...@so...> To: ny...@ny... Greetings, You are receiving this mail because you are a project admin for a SourceForge.net-hosted project. One of our primary services, CVS, suffered a series of interrelated, critical hardware failures in recent weeks. We understand how frustrating this CVS outage must be to you and your users; however, our top priority remains preservation of the integrity of your data. The series of CVS hardware failures prompted us to expedite the deployment of planed improvements to our CVS infrastructure, drawing upon much of the knowledge that we gained from our Subversion deployment. Our improved CVS service architecture, which we plan to deploy tomorrow afternoon (2006-05-12), will offer greater performance and stability and will eliminate several single points of failure. The Site Status page (https://www.sf.net/docs/A04) will be updated as soon as the new infrastructure is rolled out. In the interim, please read the important information provided below to learn about how these changes will affect your project. Summary of changes, effective 2006-05-12: 1. Hostname for CVS service Old: cvs.sourceforge.net New: PROJECT_UNIX_NAME.cvs.sourceforge.net This change will require new working copies to be checked out of all repositories (so control files in the working copy will point to the right place). We will be updating the instructions we supply, but instructions that your team has written within documentation, etc. will need to be updated. cvs -d:pserver:ano...@cv...:/cvsroot/gaim co gaim would be changed to cvs -d:pserver:ano...@ga...:/cvsroot/gaim co gaim 2. ViewCVS We are moving from ViewCVS to its successor, ViewVC. ViewVC is currently in use for our Subversion service. 3. Sync delay Old: CVS pserver, tarballs and ViewCVS provided against a separate server which is a minimum of three hours behind developer CVS. New: ViewVC will be provided against developer CVS (it will be current). CVS pserver will be provided against a secondary server (not developer server) with a maximum expected delay of two hours. Follow-up work is planned (this infrastructure takes us 80% of the way) to essentially eliminate the sync delay. 4. Read-only rsync service As a new service offering, we are now providing read-only rsync access against developer CVS. This allows projects to efficiently make on-demand backups of their entire CVS repository. All projects should be making regular backups of their CVS repository contents using this service. 5. Nightly tarball service Nightly tarball service is being dropped in lieu of read-only rsync service. Projects which currently depend on nightly tarballs for repository backups will need to begin using rsync to make a backup copy of their repository contents. We see this as a major functional improvement. For a number of reasons, tarballs have fallen out of sync with the data in the repository at times in the past few years. Tarballs required a substantial amount of additional disk, and I/O to generate. The move to read-only rsync allows backups to be produced on-demand, with an update frequency chosen by the project. 6. Points of failure In the past, developer CVS service for all projects was provided from a single host. CVS pserver service was provided from individual backend heads based on a split of the data. Under our new design, developer CVS and most of our CVS-related services are provided from one of ten CVS hosts (count subject to increase with growth). Each host is independent, and makes a backup copy of the repository data of another host (which is used to provide the pserver CVS service). Failure of a single host will impact only the availability of data on that host. Since the data is split among a larger number of hosts, the size of data impacted by an individual host outage is substantially smaller, and the time required for us to restore service will be substantially shorter. This rapid architecture change has been made possible specifically using the research we performed for our recent launch of Subversion service. We've applied our best practices, produced a substantial amount of internal documentation, and kept an eye toward maintainability. This effort has allowed us to deploy this new architecture quickly once hardware was received, and will permit us to quickly scale this service horizontally as growth and demand requires. Many other minor improvements have also been made to improve the service offering and make it less trouble-prone. The most important of which are listed above. For a full description of the new service offering, and for information on how to use the services described above, please refer to the site documentation for the CVS service after the service has been launched: https://www.sf.net/docs/E04 Thank you, The SourceForge.net Team . |
From: nyaochi <ny...@ny...> - 2006-05-05 09:48:22
|
Hi Barry, Thank you for the report. This was found to be a bug appearing only on POSIX-like environments. I made a mistake in the code, but snprintf implementation of MSVCRT hides the mistake. The MSVCRT implementation of snprintf is in danger of a buffer-overflow. I attach a patch to fix this problem. The patch has already been applied to the CVS. It was also good to know that you could build the source code on MacOS X. Thanks, Nyaochi --- Index: common/easyh10_tuner.c =================================================================== RCS file: /cvsroot/easyh10/easyh10/common/easyh10_tuner.c,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- common/easyh10_tuner.c 30 Apr 2006 11:59:35 -0000 1.6 +++ common/easyh10_tuner.c 5 May 2006 09:34:20 -0000 1.7 @@ -20,7 +20,7 @@ * */ -/* $Id: easyh10_tuner.c,v 1.6 2006/04/30 11:59:35 nyaochi Exp $ */ +/* $Id: easyh10_tuner.c,v 1.7 2006/05/05 09:34:20 nyaochi Exp $ */ #ifdef HAVE_CONFIG_H #include <config.h> @@ -266,8 +266,18 @@ if (is_storing) { if (validate_tuner_frequency(tuner->region, tuner->stations[i].frequency)) { double frequency = tuner->stations[i].frequency / 1000000. + 0.005; - snprintf(freq_integer, 3, "%03d", (int)frequency); - snprintf(freq_fractional, 2, "%02d", (int)((frequency - (double)(int)frequency) * 100.0)); + snprintf( + freq_integer, + sizeof(freq_integer), + "%03d", + (int)frequency + ); + snprintf( + freq_fractional, + sizeof(freq_fractional), + "%02d", + (int)((frequency - (double)(int)frequency) * 100.0) + ); } else { strcpy(freq_integer, "000"); strcpy(freq_fractional, "00"); |
From: nyaochi <ny...@ny...> - 2006-05-02 05:41:35
|
Hi all, I uploaded EasyH10 1.4 release candidate at: http://easyh10.sourceforge.net/dev/1.4/easyh10-1.4.tar.gz This is the change log for this release (CUI only): - Added importing/exporting function of tuner presets. - Supported Regular Expression Playlist (REP). - Supported H10 UMS 5GB/6GB firmware 2.52 officially. I tested this release on the compile firm at sourceforge.net. It would be very appreciated if you could test this release in your environment as this release is not a bug-fix release but contains major enhancements. Should you found a problem with this release, please report it to this development list. I'm planning to release it around next Sunday. Information for the package maintainers: - EasyH10 1.4 requires regex library for Regular Expression Playlist - EasyH10 1.4 now has "tuner" directory and samples of the tuner presets (*.fmr) Best regards, Nyaochi |
From: SourceForge.net <no...@so...> - 2006-05-01 12:52:06
|
Support Requests item #1479719, was opened at 2006-05-01 21:22 Message generated for change (Comment added) made by nyaochi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=742397&aid=1479719&group_id=138812 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v1.0 (example) Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: MDJUKE Initial Comment: Hi Just found out about your software for the MDJUKE. Finally I can get rid of Musicmatch and mdeiaplayer! Thanx But I got a little question: is there a chance that the mdjuke-project gets updated? or is the development stopped? Greetz Björn ---------------------------------------------------------------------- >Comment By: Nyaochi (nyaochi) Date: 2006-05-01 21:52 Message: Logged In: YES user_id=992421 Hi, I'm preparing a new project that supports MDJUKE: http://nyaochi.sakura.ne.jp/xoops/modules/mydownloads/singlefile.php?cid=1&lid=13 Nyaochi ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=742397&aid=1479719&group_id=138812 |
From: SourceForge.net <no...@so...> - 2006-05-01 12:22:58
|
Support Requests item #1479719, was opened at 2006-05-01 05:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=742397&aid=1479719&group_id=138812 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v1.0 (example) Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: MDJUKE Initial Comment: Hi Just found out about your software for the MDJUKE. Finally I can get rid of Musicmatch and mdeiaplayer! Thanx But I got a little question: is there a chance that the mdjuke-project gets updated? or is the development stopped? Greetz Björn ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=742397&aid=1479719&group_id=138812 |
From: SourceForge.net <no...@so...> - 2006-03-17 12:53:00
|
Feature Requests item #1452289, was opened at 2006-03-17 14:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=742399&aid=1452289&group_id=138812 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: David Kohen (dudyk) Assigned to: Nobody/Anonymous (nobody) Summary: Hebrew and Arabic support Initial Comment: We neet to enable reversing the letters in Hebrew and Arabic in order to overcome the H10 Unicode Bi-Di Bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=742399&aid=1452289&group_id=138812 |
From: nyaochi <ny...@ny...> - 2006-02-11 14:39:36
|
Hi all, First of all, I'd like to introduce Barry Wardell, who is working on the Cocoa GUI frontend for EasyH10. He's already become a member of EasyH10 project as a developer and comitted his work continuously into the CVS. I'd like to express a warm welcome to Barry on behalf of EasyH10 project members. It's been for about two months since the last release (1.2.1). The version seems to be so stable that I didn't get any confirmed bug report for 1.2.1. However, the firmware version 2.51 still has a trouble of shuffle playback and some users complained that they didn't get all music randomly played. To improve this situation by enhancing playlist conversion, I'm planning a new version 1.3. Here's the release plan: - (done) [common] Automatic shuffling playlist (*.sfl.*) - (done) [common] Regular Expression Playlist (*.rep) - (done) [Win32 GUI] Hebrew translation - (nearly done?) [Cocoa GUI] Releasing MacOS binary with barrywardell's frontend - (not yet) [common] Converter for tuner presets - (not yet) [common] Testing especially to check REP functionality and build problem - (skipping?) [Win32 GUI] Dutch translation if it's submitted. The support of Regular Expression Playlist requires a dependency to regex library and might break the build system. I confirmed that the current CVS HEAD could be built successfully at least on Fedore Core 2. It would be much appreciated if you could test the CVS version in your platform and let me know the result. Thanks, Nyaochi |
From: nyaochi <ny...@ny...> - 2005-11-25 01:08:42
|
Hi all, EasyH10 1.2.1 was released with a very very minor bug-fix. I'm waiting for more bug reports to arrive, but most of them were false alerms. So I released EasyH10 1.2.1 today even though it fixes one crash issue. http://easyh10.sourceforge.net/news.html In addition, RPM and SRPM packages were provided by a contributor. Thanks, Nyaochi |
From: nyaochi <ny...@ny...> - 2005-10-31 00:27:12
|
Hi all, I released EasyH10 1.2 today mainly to support new UMS/MTP firmware released by iriver last week. The source code for 1.2 release is in "branch_1_2" branch in the CVS tree. Although the CVS head contains a code to convert a text file into Tuner.dat to modify a tuner preset, I removed this code for 1.2 release because an inclusion of this new function requires updates of language texts. easyh10-cvs mailing list is now working. You can easily check the changes to the CVS chronologically: http://sourceforge.net/mailarchive/forum.php?forum_id=46715 Cheers, Nyaochi |
From: nyaochi <ny...@ny...> - 2005-10-22 10:03:28
|
1.1.1 is released in sf.net. I'll update the web page soon. # I changed the reply-to field in this list. Regards, Nyaochi nyaochi wrote: > Unfortunately, I'm about to release 1.1.1 to fix this bug: > http://easyh10.sourceforge.net/forum/index.php?topic=25.msg220#msg220 > > Nyaochi > > nyaochi wrote: > >>Hi all, >> >>Just to let you know that I've just released EasyH10 1.1 for H10 20GB >>MTP firmware 2.50. I bumped the minor version number because I had to >>modify the source code in many places even for the minor change of >>database specification. EasyH10 1.0 was only eleven-days long. And >>iRiver is planning to update H10 5/6GB UMS firmware soon... >> >>Best regards, >>Nyaochi >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: >>Power Architecture Resource Center: Free content, downloads, discussions, >>and more. http://solutions.newsforge.com/ibmarch.tmpl >>_______________________________________________ >>Easyh10-devel mailing list >>Eas...@li... >>https://lists.sourceforge.net/lists/listinfo/easyh10-devel > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Easyh10-devel mailing list > Eas...@li... > https://lists.sourceforge.net/lists/listinfo/easyh10-devel |
From: nyaochi <ny...@ny...> - 2005-10-21 20:21:58
|
Unfortunately, I'm about to release 1.1.1 to fix this bug: http://easyh10.sourceforge.net/forum/index.php?topic=25.msg220#msg220 Nyaochi nyaochi wrote: > Hi all, > > Just to let you know that I've just released EasyH10 1.1 for H10 20GB > MTP firmware 2.50. I bumped the minor version number because I had to > modify the source code in many places even for the minor change of > database specification. EasyH10 1.0 was only eleven-days long. And > iRiver is planning to update H10 5/6GB UMS firmware soon... > > Best regards, > Nyaochi > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Easyh10-devel mailing list > Eas...@li... > https://lists.sourceforge.net/lists/listinfo/easyh10-devel |
From: nyaochi <ny...@ny...> - 2005-10-21 01:17:08
|
Hi all, Just to let you know that I've just released EasyH10 1.1 for H10 20GB MTP firmware 2.50. I bumped the minor version number because I had to modify the source code in many places even for the minor change of database specification. EasyH10 1.0 was only eleven-days long. And iRiver is planning to update H10 5/6GB UMS firmware soon... Best regards, Nyaochi |
From: <ny...@ny...> - 2005-10-10 14:14:13
|
Hi all, I've just released EasyH10 1.0. Thank you very much for having always been supporting EasyH10 project. Cheers, Nyaochi |
From: nyaochi <ny...@ny...> - 2005-10-07 23:03:34
|
Then we will release it as 1.0. The minor bug-fix version will be 1.0.1, 1.0.2, ... So name it as 1.0.0 or whatever for your Debian package. Thanks, Nyaochi Benjamin Seidenberg wrote: > nyaochi wrote: > > >>>Would it be possible/have you considered having the official version as >>>1.0.0 instead of 1.0? Reasons: >>> >>>* Bugfixes could be increments of the minor revision (1.0.1, 1.0.2, etc) >>>while adding features could bump the major revision (1.1.x, 1.2.x..) >>>* The above makes it easier to keep track of versions >>>* I screwed up, current version in debian is 1.0b7-1, and 1.0-1 < >>>1.0b7-1 < 1.0.0-1 so if it's 1.0 i'd either change the number for debian >>>or do it as 1.0final-1. >>> >>> >> >>I thought version numbers should be 1.0 (released with confidence) -> >>1.0.1 (but found minor bugs) -> 1.0.2. I don't like 1.0.0 because it >>presumably says there will be a bug-fix release in the future. But I >>understand the situation of "1.0b7-1 > 1.0", so I don't mind releasing >>1.0 as 1.0.0. >> >>Nyaochi >> >> > > I think it depends on the convention you use (there are several) and > should just be consistant. Either way works, I can do something fun with > the debian version (1.0final) or something. They need that ~ operator! > It's up to you |
From: Benjamin S. <ast...@dl...> - 2005-10-07 02:46:12
|
nyaochi wrote: >>Would it be possible/have you considered having the official version as >>1.0.0 instead of 1.0? Reasons: >> >>* Bugfixes could be increments of the minor revision (1.0.1, 1.0.2, etc) >>while adding features could bump the major revision (1.1.x, 1.2.x..) >>* The above makes it easier to keep track of versions >>* I screwed up, current version in debian is 1.0b7-1, and 1.0-1 < >>1.0b7-1 < 1.0.0-1 so if it's 1.0 i'd either change the number for debian >>or do it as 1.0final-1. >> >> >I thought version numbers should be 1.0 (released with confidence) -> >1.0.1 (but found minor bugs) -> 1.0.2. I don't like 1.0.0 because it >presumably says there will be a bug-fix release in the future. But I >understand the situation of "1.0b7-1 > 1.0", so I don't mind releasing >1.0 as 1.0.0. > >Nyaochi > > I think it depends on the convention you use (there are several) and should just be consistant. Either way works, I can do something fun with the debian version (1.0final) or something. They need that ~ operator! It's up to you |
From: nyaochi <ny...@ny...> - 2005-10-07 02:42:06
|
> Would it be possible/have you considered having the official version as > 1.0.0 instead of 1.0? Reasons: > > * Bugfixes could be increments of the minor revision (1.0.1, 1.0.2, etc) > while adding features could bump the major revision (1.1.x, 1.2.x..) > * The above makes it easier to keep track of versions > * I screwed up, current version in debian is 1.0b7-1, and 1.0-1 < > 1.0b7-1 < 1.0.0-1 so if it's 1.0 i'd either change the number for debian > or do it as 1.0final-1. I thought version numbers should be 1.0 (released with confidence) -> 1.0.1 (but found minor bugs) -> 1.0.2. I don't like 1.0.0 because it presumably says there will be a bug-fix release in the future. But I understand the situation of "1.0b7-1 > 1.0", so I don't mind releasing 1.0 as 1.0.0. Nyaochi |
From: Benjamin S. <ast...@dl...> - 2005-10-07 02:17:24
|
nyaochi wrote: >Hi all, > >I prepared EasyH10 1.0 RC 1: >http://easyh10.sourceforge.net/dev/1.0rc1/easyh10-1.0rc1.tar.gz >ChangeLog: >* [POSIX CUI] Fixed a bug that playlist conversion fails when playlist >files point to a great number of music files. Many thanks for providing >a test environment, Benjamin. >* [CUI] Added new option -I (--install) to copy a model template file >specified by -t option into the player as "easyh10.model". >* [CUI] EasyH10 now assumes that the model template file specified by -t >option exists in on of the following locations: (current directory), >"/usr/local/share/easyh10/model/", "/usr/local/share/easyh10/", >"/usr/share/easyh10/model/", and "/usr/share/easyh10/". >* [CUI] "make install" now installs documents such as README, COPYING, etc. >* [Web site] All web contents are improved in terms of English >presentation by BirdFish. >* [Web site] Updated EasyH10 logo. > >I decided the release date of EasyH10 1.0 as 10 October 2005 because the >date contains two "10". It would be great if you could check this >version and prepare the upcoming 1.0 release. I will provide 1.0 final >with you around the midnight of 9 October in UK local time. > >Best regards, >Nyaochi > > Would it be possible/have you considered having the official version as 1.0.0 instead of 1.0? Reasons: * Bugfixes could be increments of the minor revision (1.0.1, 1.0.2, etc) while adding features could bump the major revision (1.1.x, 1.2.x..) * The above makes it easier to keep track of versions * I screwed up, current version in debian is 1.0b7-1, and 1.0-1 < 1.0b7-1 < 1.0.0-1 so if it's 1.0 i'd either change the number for debian or do it as 1.0final-1. Benjamin |
From: nyaochi <ny...@ny...> - 2005-10-07 01:45:51
|
Hi all, I prepared EasyH10 1.0 RC 1: http://easyh10.sourceforge.net/dev/1.0rc1/easyh10-1.0rc1.tar.gz ChangeLog: * [POSIX CUI] Fixed a bug that playlist conversion fails when playlist files point to a great number of music files. Many thanks for providing a test environment, Benjamin. * [CUI] Added new option -I (--install) to copy a model template file specified by -t option into the player as "easyh10.model". * [CUI] EasyH10 now assumes that the model template file specified by -t option exists in on of the following locations: (current directory), "/usr/local/share/easyh10/model/", "/usr/local/share/easyh10/", "/usr/share/easyh10/model/", and "/usr/share/easyh10/". * [CUI] "make install" now installs documents such as README, COPYING, etc. * [Web site] All web contents are improved in terms of English presentation by BirdFish. * [Web site] Updated EasyH10 logo. I decided the release date of EasyH10 1.0 as 10 October 2005 because the date contains two "10". It would be great if you could check this version and prepare the upcoming 1.0 release. I will provide 1.0 final with you around the midnight of 9 October in UK local time. Best regards, Nyaochi |
From: Benjamin S. <ast...@dl...> - 2005-09-29 20:11:45
|
ny...@us... wrote: >Hi all, > >As we are preparing EasyH10 1.0 RC, it's a good occasion to discuss the >packaging ambiguity. > >Do you think we should include an HTML manual into the binary distribution >or not? The HTML manual will be the copy of the web pages. I don't think >we need it because: we already have manpage; HTML pages in /usr/share are >seldom referred; the manual (with PNG images) will be larger than the >binary; and most computers running on Linux have the Internet connection. > > > I think that most distributions will use the source package to create their own binary package, and if someone downloads a binary distribution from SF they have the net. Another possibility would be to create a -doc package, so you have source+doc, doc and binary. Up to you. >Another question. Where is the most suitable location to put README, >COPYING, AUTHORS, INSTALL, etc? >a) /usr/share/easyh10/doc >b) /usr/share/doc >c) Nowhere (do not install these files) >I saw a Gentoo Linux user who is going to install these files into b). >http://www.misticriver.net/showthread.php?t=29501 > > > Debian policy mandates /usr/share/doc/<package-name>, but that's handled by my install scripts anyway. >EasyH10 is now becomming a bit famous among linux distributions. I know >it's up to the maintainers and distributions, but IMHO the project should >avoid the chaotic situation beforehand by showing the standard in >Makefile.am. > > Check if autoconf/make has a default, if so, use it, I think there's a flag for it for my packages to override it when they build >Best regards, >Nyaochi > > > > Cheers, Benjamin |
From: <ny...@us...> - 2005-09-29 17:50:22
|
Hi all, As we are preparing EasyH10 1.0 RC, it's a good occasion to discuss the packaging ambiguity. Do you think we should include an HTML manual into the binary distribution or not? The HTML manual will be the copy of the web pages. I don't think we need it because: we already have manpage; HTML pages in /usr/share are seldom referred; the manual (with PNG images) will be larger than the binary; and most computers running on Linux have the Internet connection. Another question. Where is the most suitable location to put README, COPYING, AUTHORS, INSTALL, etc? a) /usr/share/easyh10/doc b) /usr/share/doc c) Nowhere (do not install these files) I saw a Gentoo Linux user who is going to install these files into b). http://www.misticriver.net/showthread.php?t=29501 EasyH10 is now becomming a bit famous among linux distributions. I know it's up to the maintainers and distributions, but IMHO the project should avoid the chaotic situation beforehand by showing the standard in Makefile.am. Best regards, Nyaochi |