The newest (unstable) ebuild for this awesome text editor is 3.3.18b. I have therefore created an ebuild for the most current 5.0.1 version which offers great improvements over the older version, especially UNICODE support. I took the old ebuild as a basis and added all required changes for the new version to compile, build and install fine. I also added an "iconv" USE flag because of the new version's improved capabilities. The new version also introduced build-time dependencies on another tool; I have created an ebuild for that, too. Reproducible: Always Steps to Reproduce: All ebuilds have been tested in my local Portage overlay and on my machine (x86) and work as expected. Please consider using my ebuilds as a basis for adding remastered versions of them to the official tree. I have no CVS access and cannot use the echangelog utility - so I have omitted any ChangeLog files. metadata.xml files might also be necessary. And I cannot do testing for other platforms, although I doubt there will be problems. Here is the layout of the ebuilds: app-editors/mp-5.0.1: This is the actual editor component. Is has two dependencies: app-doc/mp_doccer (new; see below) and app-text/grutatxt (I used the newest version 2.0.13 but didn't enforce a specific version in the ebuild). app-doc/mp_doccer: Documentation generator required for building the editor Patches for the files/* required by this ebuild: p01-changelog.patch p02-ownership.patch
Created attachment 140977 [details] Ebuild for the "Minimum Profit" text editor component
Created attachment 140978 [details] Documentation Generator required for building the editor
Created attachment 140980 [details, diff] Patch for missing upstream CVS when generating ChangeLog Patch for mp_doccer
Created attachment 140981 [details, diff] Required if building as "portage" user rather than root Patch for mp_doccer
(In reply to comment #2) > Created an attachment (id=140978) [edit] > Dlc Typo (pressed Enter too soon); this should read > Documentation Generator required for building the editor
this is actually a bump request, mp has been in the tree for years
(In reply to comment #6) > this is actually a bump request, mp has been in the tree for years Yes. Sorry - I did not know that bump requests should be handled differently. If someone knows how to change the status of this bug entry accordingly, please feel free to do so. BTW, if I find some time in the next couple of days I will check if upstream has an even newer version right now. It's been nearly a year since I created the ebuild.
(I was inspired by seeing other devs work on the maintainer-needed queue) I took your mp-5.0.1 ebuild, renamed it to 5.1.1, changed the mp_doccer dep to grutatxt and emerged it with USE=-gtk...works! There was far too many deps to test with USE=gtk in my chroot. Could you test it out and file new bugs if needed? Thanks for your work and sorry it took a year to commit! =/
(In reply to comment #8) > I took your mp-5.0.1 ebuild, renamed it to 5.1.1, changed the mp_doccer dep to > grutatxt Problem is: grutaxt is not the same as my mp_doccer! Actually, I also have a app-text/grutatxt in my overlay, but app-doc/mp_doccer is a different ebuild. Here is eix output: ======snip======= * app-text/grutatxt Available versions: *2.0.5 ~*2.0.11 ~*2.0.13 *2.0.13[1] Homepage: http://triptico.com/software/grutatxt.html Description: A converter from plain text to HTML and other markup languages [1] /usr/portage/local/layman/xworld xquad ~ # eix mp_doccer * app-doc/mp_doccer [1] Available versions: *1.2.0 Homepage: http://triptico.com/software/grutatxt.html Description: C Source Documentation Generator for Minimum Profit editor [1] /usr/portage/local/layman/xworld ======snip======= If you want to examine my grutaxt ebuild fromt the overlay, you can add it using # layman -o http://rpo.xw.ath.cx/gentoo/portage/overlays/xworld.xml -a xworld (requires >=dev-util/bzr-1.6.1 for checking out)
Oh, interesting. I didn't understand what the difference was. mp built and successfully ran without mp_doccer and grutatxt instead (its in the portage tree, so I'm not sure why you need a overlay for it. I'll have to fix this later, busy for the next few days here.
(In reply to comment #10) > tree, so I'm not sure why you need a overlay for it. Only because of the different version numbers! I wanted all ebuilds to share the same amount of up-to-dateness.
(In reply to comment #11) > Only because of the different version numbers! I wanted all ebuilds to share > the same amount of up-to-dateness. Oops, it just occurred to me that the version numbers are actually the same! ;-) The only actual reason was a site-local override of the KEYWORDS. Which means the grutaxt ebuild from the official tree should work as well.
(In reply to comment #12) > Which means the grutaxt ebuild from the official tree should work as well. Ok, then this bug can be closed again? Sorry, I'm still slightly confused because mp builds fine for me without mp_doccer.
(In reply to comment #13) > Ok, then this bug can be closed again? Sorry, I'm still slightly confused > because mp builds fine for me without mp_doccer. I updated the ebuilds to the newest upstream versions today. And indeed you are right, it seems mp_doccer is not actually used by the mp build. I am not certain whether this is new behavior by the new version or has been the case ever since. Maybe I was misled by the fact that mp_doccer invocations are present in several build scripts included within the distribution archive. But it seems that those scripts are not actually used by the build process as pre-built documentation files (generated by mp_doccer) are included within the distribution tarball already. I have therefore removed the mp_doccer build dependency just as you suggested, and will post the updated ebuilds as the next bugzilla comment. The mp_doccer ebuild can thus be ignored for mp; I'll post an add-request for it as an independent ebuild (because I have already created an ebuild for its newest version which would be a shame to just throw away).
Created attachment 177915 [details] The ebuild for the newest version as of 2009-01-01 mp_doccer buildtime-dependency has been removed. Tested on amd64 and supposed to work on x86 also. Ebuild =app-text/grutatxt-2.0.14 was used as an actual dependency.
(In reply to comment #15) > Created an attachment (id=177915) [edit] > The ebuild for the newest version as of 2009-01-01 > > mp_doccer buildtime-dependency has been removed. > > Tested on amd64 and supposed to work on x86 also. > > Ebuild =app-text/grutatxt-2.0.14 was used as an actual dependency. > 5.1.1 is *in* the tree already. Thanks for the follow up, I'll resolve this bug now.
(In reply to comment #16) > 5.1.1 is *in* the tree already. Thanks for the follow up, I'll resolve this bug > now. Very fine! And FYI, I have just added a bump-request for =app-text/grutatxt-2.0.14.
