Last night SchAmane and I have developed an ebuild that builds jscall-sharp from SVN repository. It provides support for either mozilla and mozilla-firefox. jscall-sharp is a JavaScript bridge for gecko-sharp. Due to it's early development stage version number 9999 was chosen. dev-dotnet/jscall-sharp suggested.
Created attachment 97171 [details] jscall-sharp-9999.ebuild (New package) The ebuild itself
Created attachment 97172 [details, diff] Patch #1
Created attachment 97173 [details, diff] Patch #2
Have there not been any tarball releases of this library? If not, it's much prefered to do a SVN snapshot, using the current version number (usually found in the configure.ac file) and something like jscall-sharp-0.2_pre20060925.ebuild to deal with this. Also, I'd much prefer to actually fix the autotools stuff to make their install work with a GACUTILS_FLAGS variable like upstream gtk-sharp tarball currently uses.The advantage being we can submit such a patch upstream, and down the line not have to worry about it.
Created attachment 98072 [details] jscall-sharp-0.2_pre20050925.ebuild Updated ebuild. It doesn't use SVN anymore, includes more dependencies and introduces a normalized versioning system (instead of 9999). Forces src/Makefile.am to use the GACUTILS_FLAG instead of installing assemblies into GAC manually in ebuild.
Created attachment 98073 [details] jscall-sharp-0.2_pre20050925.tar.bz2 A tarball with svn snapshot included.
Created attachment 98074 [details, diff] jscall-sharp-gacfix.diff Replaces previous gac patch (Patch #2)
The uninstall-local target in the one patch seems a little off.. Should be $(GACUTIL) $(GACUTIL_FLAGS) like in the install-local target. Also, it seems that configure.ac from jscall-sharp considers CVS to currently be 0.0.2, not just 0.2. Lastly, it seems the jscall-sharp.pc file is expecting this in @libdir@/jscall-sharp/... Can you confirm the .pc file ends up pointing to the right spot? In particular, this probably means that the gacutil argument should be /package ${PN}, not ${PN}-0.2, so the symlinks in /usr/$(get_libdir)/mono/${PN}/ are in the right spot. Otherwise, this looks much better.
(In reply to comment #8) > The uninstall-local target in the one patch seems a little off.. Should be > $(GACUTIL) $(GACUTIL_FLAGS) like in the install-local target. True, I don't know why did that happen ;) > Also, it seems > that configure.ac from jscall-sharp considers CVS to currently be 0.0.2, not > just 0.2. I simply followed your suggestion regarding the version number. Indeed, this should be 0.0.2. > Lastly, it seems the jscall-sharp.pc file is expecting this in > @libdir@/jscall-sharp/... Can you confirm the .pc file ends up pointing to the > right spot? In particular, this probably means that the gacutil argument > should be /package ${PN}, not ${PN}-0.2, so the symlinks in > /usr/$(get_libdir)/mono/${PN}/ are in the right spot. Otherwise, this looks > much better. Here's what's being merged: >>> Merging dev-dotnet/jscall-sharp-0.2_pre20050925 to / --- /usr/ --- /usr/lib/ >>> /usr/lib/libjscallglue-0.0.2.so >>> /usr/lib/libjscallglue.so -> libjscallglue-0.0.2.so >>> /usr/lib/libjscallglue.la >>> /usr/lib/libjscallglue.a --- /usr/lib/mono/ --- /usr/lib/mono/gac/ --- /usr/lib/mono/gac/jscall/ --- /usr/lib/mono/gac/jscall/0.0.2.0__db10596f4718e9c9/ >>> /usr/lib/mono/gac/jscall/0.0.2.0__db10596f4718e9c9/jscall.dll >>> /usr/lib/mono/gac/jscall/0.0.2.0__db10596f4718e9c9/jscall.dll.config >>> /usr/lib/mono/gac/jscall/0.0.2.0__db10596f4718e9c9/jscall.dll.mdb --- /usr/lib/mono/jscall-sharp-0.2/ >>> /usr/lib/mono/jscall-sharp-0.2/jscall.dll -> ../gac/jscall/0.0.2.0__db10596f4718e9c9/jscall.dll --- /usr/lib/jscall-sharp/ >>> /usr/lib/jscall-sharp/jscall.dll.mdb >>> /usr/lib/jscall-sharp/jscall.dll >>> /usr/lib/jscall-sharp/JSCall.js >>> /usr/lib/jscall-sharp/jscall.dll.config --- /usr/lib/pkgconfig/ >>> /usr/lib/pkgconfig/jscall-sharp.pc --- /usr/share/ --- /usr/share/doc/ --- /usr/share/doc/jscall-sharp-0.2_pre20050925/ >>> /usr/share/doc/jscall-sharp-0.2_pre20050925/ChangeLog.gz >>> /usr/share/doc/jscall-sharp-0.2_pre20050925/README.gz >>> /usr/share/doc/jscall-sharp-0.2_pre20050925/COPYING.gz >>> /usr/share/doc/jscall-sharp-0.2_pre20050925/AUTHORS.gz From /usr/lib/pkgconfig/jscall-sharp.pc: prefix=/usr exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Libraries=${exec_prefix}/lib/jscall-sharp/jscall.dll Script=${exec_prefix}/lib/jscall-sharp/JSCall.js MozillaHome=/usr/lib/mozilla-firefox Name: jscall-sharp Description: jscall-sharp - Limited JavaScript bridge for Gecko# Version: 0.0.2 Libs: -r:${exec_prefix}/lib/jscall-sharp/jscall.dll Hence all .pc entries are valid. The only entries that are being affected by the /package ${PN}-0.2 are: --- /usr/lib/mono/jscall-sharp-0.2/ >>> /usr/lib/mono/jscall-sharp-0.2/jscall.dll -> ../gac/jscall/0.0.2.0__db10596f4718e9c9/jscall.dll Also please notice that packages such as gecko-sharp or gtk-sharp take the same approach (with version number) and it seems to be valid. Give me a minute to post the corrections.
Created attachment 98362 [details] jscall-sharp-0.0.2_pre20050925.ebuild Ebuild with corrected version number. No internal changes
Created attachment 98363 [details] jscall-sharp-0.0.2_pre20050925.tar.bz2 Tarball with corrected version number.
Created attachment 98364 [details, diff] jscall-sharp-gacfix.diff The gacfix patch with Peter's suggestions included.
Fixed in CVS, thanks
Created attachment 101974 [details] dev-dotnet/jscall-sharp-0.0.2.ebuild accordling to Michael Hutchinson (jscall-sharp developer), jscall-sharp is gone outside the beta testing and he just provide .deb packages for testing purposes before to release the 0.0.2 version as stable. attached there is a new ebuild that use the last repository version and fix the dependencies to use seamonkey instead of the old (and deprecated) mozilla suite, making jscall-sharp more portage compliant and ready for the new "seamonkey rules".
Created attachment 101975 [details, diff] geckos_configure_fix.patch patch that fix configure.ac to rely only to seamonkey, firefox and xulrunner, discarding the old mozilla checks and stuff.
Created attachment 101978 [details] jscall-sharp-0.0.2.tar.bz2 tarball containing the latest repository version
Thanks for your input. However, next time file a new bug, please. There is also one thing to be corrected in src_install(): '/package ${PN}-0.2' should be changed to '/package ${PN}-0.0.2'.
Ok, I'm not putting the suggested 0.0.2 version into portage with this version number unless it gets official. However, I've just made a fresh svn snapshot (20061125), used your geckos_configure_fix.patch and committed them to the tree a while ago.