Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
New ebuild Reproducible: Always
Please note that we do keep up with the releases; there is no need to file bug reports for version bumps immediately. We are working on getting monodevelop-0.13 into portage.
(In reply to comment #1) > Please note that we do keep up with the releases; there is no need to file bug > reports for version bumps immediately. We are working on getting > monodevelop-0.13 into portage. > Any chance to get a status update? 0.13.1 has even been released :)
(In reply to comment #2) > (In reply to comment #1) > > Please note that we do keep up with the releases; there is no need to file bug > > reports for version bumps immediately. We are working on getting > > monodevelop-0.13 into portage. > > > > Any chance to get a status update? 0.13.1 has even been released :) > You can (mis)use the monodevelop-0.12.ebuild. Create a local Overlay and copy this ebuild. Rename it to monodevelop-0.13.1.ebuild and remove the fixes section. Digest and emerge. The IDE works, C# works, the GTK-Designer works. I have not tested anything else. Maybe you can use this procedure with the 0.12-r6 ebuild from the WiredTEK overlay.
Created an attachment (id=115110) [details] monodevelop-0.13.1 custom ebuild
(From update of attachment 115110 [details]) Thanks Thomas, that worked. Still, it would be nice to see a "native" ebuild :)
Created an attachment (id=115134) [details] monodevelop-0.13.1.ebuild based on wtk-overlay version compiles ok and seems to be working with: USE="aspnet firefox subversion -boo -debugger -java -seamonkey -vte" makefile patch can be obtained from http://wtk-overlay.svn.sourceforge.net/viewvc/wtk-overlay/wtk-mono/dev-util/monodevelop/files/monodevelop-0.12-makeinstall-fix.diff?revision=194&view=markup
I also tried to enable nemerle support, but got some errors ( see http://bugzilla.ximian.com/show_bug.cgi?id=81282 )
Created an attachment (id=115201) [details] monodevelop-0.13.1.ebuild (based on wtk-overlay) removed debugger flag (monodebugger is not in portage)
Created an attachment (id=115378) [details] monodevelop-0.13.1-nemerle-fix.diff patch for nemerle plugin seems to work, but without autocomplete support
Created an attachment (id=115380) [details] monodevelop-0.13.1.ebuild (with nemerle support) monodevelop ebuild with nemerle support requires nemerle-dev snapshot ( http://bugs.gentoo.org/show_bug.cgi?id=173264 )
I tried the latest of these ebuilds without luck. I had to remove the monodevelop-0.12-makeinstall-fix.diff line from the ebuild, as the file was neither in this buggreport nor in portage. Anyway, the error I got is pasted below: make[5]: Entering directory `/var/tmp/portage/dev-util/monodevelop-0.13.1/work/monodevelop-0.13.1/Extras/AspNetEdit/chrome' cp aspdesigner.jar /usr/lib64/mozilla-firefox/chrome/ if test -f /usr/lib64/mozilla-firefox/chrome/installed-chrome.txt; then \ cp /usr/lib64/mozilla-firefox/chrome/installed-chrome.txt /tmp/chrome.old; \ sudo bash -c "sed -e'/aspdesigner/d' /tmp/chrome.old > /usr/lib64/mozilla-firefox/chrome/installed-chrome.txt"; \ for CHRM in "content,install,url,jar:resource:/chrome/aspdesigner.jar!/content/aspdesigner/" "locale,install,url,jar:resource:/chrome/aspdesigner.jar/locale/en-US/aspdesigner/"; do \ cp /usr/lib64/mozilla-firefox/chrome/installed-chrome.txt /tmp/chrome.old; \ sudo bash -c "sed -e'\$a$CHRM' /tmp/chrome.old > /usr/lib64/mozilla-firefox/chrome/installed-chrome.txt"; \ rm /tmp/chrome.old; \ done; \ fi; ACCESS DENIED open_wr: /usr/lib64/mozilla-firefox/chrome/aspdesigner.jar cp: cannot create regular file `/usr/lib64/mozilla-firefox/chrome/aspdesigner.jar': Permission denied make[5]: *** [old-install-files] Error 1 make[5]: *** Waiting for unfinished jobs.... /bin/sh: line 2: sudo: command not found /bin/sh: line 5: sudo: command not found /bin/sh: line 5: sudo: command not found make[5]: Leaving directory `/var/tmp/portage/dev-util/monodevelop-0.13.1/work/monodevelop-0.13.1/Extras/AspNetEdit/chrome' make[4]: *** [install-data-am] Error 2 make[4]: Leaving directory `/var/tmp/portage/dev-util/monodevelop-0.13.1/work/monodevelop-0.13.1/Extras/AspNetEdit/chrome' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/var/tmp/portage/dev-util/monodevelop-0.13.1/work/monodevelop-0.13.1/Extras/AspNetEdit/chrome' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/dev-util/monodevelop-0.13.1/work/monodevelop-0.13.1/Extras/AspNetEdit' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/dev-util/monodevelop-0.13.1/work/monodevelop-0.13.1/Extras' make: *** [install-recursive] Error 1 !!! ERROR: dev-util/monodevelop-0.13.1 failed. Call stack: ebuild.sh, line 1614: Called dyn_install ebuild.sh, line 1060: Called qa_call 'src_install' environment, line 3613: Called src_install monodevelop-0.13.1.ebuild, line 76: Called die !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/log/portage/dev-util:monodevelop-0.13.1:20070503-202629.log'. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-util_-_monodevelop-0.13.1-30198.log" open_wr: /usr/lib64/mozilla-firefox/chrome/aspdesigner.jar -------------------------------------------------------------------------------- !!! This ebuild is from an overlay: '/usr/local/portage/mono'
(In reply to comment #11) > I tried the latest of these ebuilds without luck. I had to remove the > monodevelop-0.12-makeinstall-fix.diff line from the ebuild, as the file was > neither in this buggreport nor in portage. Anyway, the error I got is pasted > below: In Comment #6 I posted a link to monodevelop-0.12-makeinstall-fix.diff http://wtk-overlay.svn.sourceforge.net/viewvc/*checkout*/wtk-overlay/wtk-mono/dev-util/monodevelop/files/monodevelop-0.12-makeinstall-fix.diff You must use that file to build monodevelop
Created an attachment (id=118093) [details] monodevelop-0.12-makeinstall-fix.diff Attaching wtk-overlay's monodevelop-0.12-makeinstall-fix.diff here
*** Bug 177600 has been marked as a duplicate of this bug. ***
Created an attachment (id=121942) [details] Version 0.14 of monodevelop Ebuild for the new version of monodevelop.
*** Bug 181988 has been marked as a duplicate of this bug. ***
Created an attachment (id=121999) [details] monodevelop-0.14 custom ebuild New ebuild for version 0.14 modified from Saleem Abdulrasool. Tested on x86 with use flags firefox and subversion.
Created an attachment (id=122000) [details] monodevelop-0.14-configure.patch Patch file belonging to ebuild attachment no. #121999.
(In reply to comment #17) > Created an attachment (id=121999) [edit] [details] > monodevelop-0.14 custom ebuild > > New ebuild for version 0.14 modified from Saleem Abdulrasool. > > Tested on x86 with use flags firefox and subversion. > works fine for me on x86 with use firefox java
Working great for me here as well! =P nice ebuild
Why did you drop the aspnet flag?
(In reply to comment #21) > Why did you drop the aspnet flag? > The original author of this ebuild dropped the flag and because I don't need it I just didn't care :). But feel free to activate the flag, test it and share your working ebuild.
One more thing (and please correct me if I'm wrong): all "fixes" introduced by monodevelop-0.14-configure.patch (attachment #122000 [details]) besides `which seamonkey` and MOZILLA_HOME lines actually prevent monodevelop from properly detecting aspnet/nemerle/boo settings passed to configure script. Any reason why?
Never mind, just ignore my last comment... too tired to do any serious bugfixing now ;-)
Created an attachment (id=123277) [details] monodevelop-0.14.ebuild with aspnet and aspnetedit support Ok, here's my version based on Tim's ebuild. New things: 1. aspnet and aspnetedit use flags + related code 2. ikvm now takes precedence over ikvm-bin 3. some code formatting issues Two patches will follow. Since we're not taking monodevelop-0.13.1 or 0.12 under consideration anymore, I'm also marking any regarding attachments obsolete. I'd like to finally add this to portage later today (maybe tomorrow), so let's stick to one version of 0.14 ebuild. Hence if you want to introduce any changes or fixes - do it basing on the one I've just sent here.
Created an attachment (id=123278) [details] monodevelop-0.14-configure.patch A modified version (more strict) of Tim's configure.patch. It doesn't allow situations, where e.g. --enable-boo is passed to configure script without boo being present in the system. Without this strict checking compilation went smoothly, now we get a configure error.
Created an attachment (id=123279) [details] patch fixing default ASP.NET (Web application) project template A small patch fixing default ASP.NET project template
Your ebuild works fine for me with aspnet use flags enabled. Good work and I am glad that monodevelop has finally found it's way back into portage :).
The only thing that still worries me is nemerle support. As far as I can see monodevelop needs a daily snapshot in order to work and I'm not sure how to handle this as those are probably quite unstable. One option is to p.mask nemerle-0.9.3.99* and thus monodevelop-0.14, another is to drop nemerle useflag, wait until a new stable version arrives and forget about p.masking. You're welcome to share your opinions.
I vote for package.masking new nemerle and package.use.masking nemerle USE flag for monodevelop-0.14.
I've decided to let nemerle go and there are (at least) three arguments to support this decision: 1. monodevelop-0.14 requires a development snapshot of nemerle 2. nemerle snapshots made from any svn revision > 6855 do not provide the Nemerle.Completion namespace required by monodevelop-0.14 (see bug #158241), hence it will most probably not reappear in next stable release; this means that either nemerle community takes on the monodevelop nemerle addin and finishes it or monodevelop upstream drops nemerle support (check out this mono-list thread: http://lists.ximian.com/pipermail/mono-list/2007-May/035137.html) 3. Extras/NemerleBinding/Gui/CodeGenerationPanel.cs seems to require mono-addins, which is fairly new and hasn't made it to portage yet My opinion is to hold back nemerle support until status of the add-in is clarified and officially confirmed by upstream
checking for update-mime-database... /usr/bin/update-mime-database checking for update-desktop-database... no configure: error: You need to install update-desktop-database Possible desktop-file-utils must be added to dependencies, or this check removed from configure
monodevelop-0.14 is in the tree now, thank you all for providing the ebuilds, patches and support. Please report any related and not yet solved problems mentioned here by filing new bugs.
