You don't need the source code of ExtInstall.jar in order to compile or modify RemoteMaster, any more than you need the source code of any other jar file in the lib directory. What are you trying to achieve?_________________Graham

I'm currently writing a build script to create a proper package for my distribution and in fact I decided to rebuild two files in the "lib" directory as they contain binary parts. I preferred to rebuild them with the compiler settings common on my distribution.

BTW: Where to send patches to? I've found at least two bugs when running on Linux and already have a patch ready for this.

If I remember correctly, ExtInstall was written by someone else, so we might not have the source. As others have said, you don't need to understand that installer in order to understand RMIR, so what is it that you're really trying to do?_________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

My primary goal is to get RemoteMaster properly built as Arch Linux package. To do this, I have to write a so-called "PKGBUILD" which does the building and finally the packaging including properly registering the new application so a new application icon gets added to the applications list.

Usually it is not recommended to just do "repackaging". If I really do the work to write a proper "build script", then this can also really use JDK to build the files and not just to repackage them. This also allows to recompile binaries. So while you currently don't have all your files for the ARM platform, my build script could create them if needed.

That's why I was interested in the source code for every bit.

On the other hand it is also a bit of a question about trust. Is it really possible to review every single part? Maybe currently not. But I'll try if the source for "ExtInstall", that I found in the downloads section, actually builds into a library that works together with RemoteMaster.

While trying to create a package and using RemoteMaster for several days now (This is really great software! Thank you very much for creating it! It really makes these cheap remotes much more fun to use!) I already found a few bugs and did fixes for them. In fact there are still two bugs left where I want to create fixes this weekend.

Currently my patches are part of my build script, which is OK for me and (as soon as I publish my PKGBUILD) also for all other Arch users. But I would prefer to somehow give the fixes back, so I'm still interested in the "proper way" to send in patches. As far as I know Sourceforge doesn't offer "Pull requests", right?

PKGBUILD's also have a variable to put the license in. I have set this to "unknown", so far as I couldn't find any information about which license you put your code under. If I remember correctly, you use at least one library which requires the software, using it, to be GPL licensed. So is GPL the right license, then? Which version? GPL2 or GPL3?

Sorry for all the questions. As far as I see, I'm the first one who is interested in creating a RemoteMaster software package and as some of the bugs, that I found, only happen on the Linux platform, I think you don't have that much Linux users either.

Regarding the bugs that you have found, my advice would be to list them in a separate post where they can be reviewed and incorporated into RMIR._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!